If you are a developer who uses containers, chances are you and your team have heard about Kubernetes. At its core, Kubernetes is a container operating system for the web, but has grown to be much more. Sure, Kubernetes can manage your containers, network traffic, and bring up a crashed ad, but it has also become a widely adopted platform with a growing community.
Congratulations!! After 3 months of hard work, your developer has done an incredible job and your brand new web application is ready to be put online. But wait a minute… Who is going to put it online? Try to ask your developer to do it - there is a good chance that he can’t. Why? Deploying applications is not necessarily a part of their qualifications. And even if he is able to, who's going to make sure it's always available and scale as your business grows?
Security is one of the most talked-about topics for Kubernetes users. Google “Kubernetes security” and you’ll find a huge number of articles, blogs and more. The reason is simple: you need to align your container and Kubernetes security with your organization’s existing security profile. Kubernetes has some strong security best practices for your cluster—authentication and authorization, encryption in secrets and objects in the etcd database—to name a few.
In Part 1 we’ve described what container monitoring is and why you need it. Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and the applications they run. These servers and applications running on them are typically very static, with very long uptimes.
Even though containers have been around for ages, it wasn’t until Docker showed up that containers really became widely adopted. Docker has made it easier, faster, and cheaper to deploy containerized applications. However, organizations that adopt container orchestration tools for application deployment face new maintenance challenges.
AWS (Amazon Web Services) is an amazing and reliable cloud service provider. AWS, like Google Cloud Platform and Microsoft Azure, provides everything you need to host an application without having to worry about running the underlying servers and network configuration. Everything you need to quickly begin hosting is provided as a packaged services.
In this blog post, you will learn how to setup image scanning with Github Actions using Sysdig Secure DevOps Platform. We will create a basic workflow to perform a local scan to detect vulnerabilities and bad practices before the image is pushed to any registry. We will also customize scanning policies to stop the build according to a set of defined rules.
Easying enterprise Kubernetes adoption is at the core of what we do. Today, we are thrilled to announce Kublr’s simplified and comprehensive role-based-access-control (RBAC) management via the Kublr UI.
At Codefresh, we know that any CI/CD solution must be attractive to both developers and operators (SREs). One of the major advantages of Codefresh is the graphical user interface that includes dashboards for Kubernetes and Helm deployments. These graphical dashboards are very useful to developers who are just getting started with deployments and pipelines.
