The latest News and Information on Containers, Kubernetes, Docker and related technologies.
Amazon EKS is the most popular managed Kubernetes solution. DevOps teams can quickly spin up clusters in the cloud and get started with Kubernetes in a few clicks. As organizations embrace Kubernetes in the cloud, the challenge becomes managing clusters across multiple regions or accounts. At that point, organizations struggle to visualize all of their clusters.
Despite the lockdown restrictions of the last six months, I'm delighted to announce that we've released Rancher 2.5 on schedule today. This latest release represents another major milestone of Rancher's "Computing Everywhere" strategy by delivering management capabilities that match the extraordinary popularity of Amazon EKS and our lightweight Kubernetes distribution, K3s.
The ability of Kubernetes to easily deploy and manage containerized software has given organizations tremendous capabilities in their cloud services, with clusters multiplying into the hundreds or thousands and extending out to the edge for any number of purposes. But its growing popularity has also led to challenges in managing complexity in an environment that is conducive to cluster sprawl.
If you are looking to account for your container costs and understand how your AWS Kubernetes or EKS cluster spend maps onto your workloads, this guide was made for you! In this post we will walk through the steps to get up and running with CloudZero and Amazon Container Insights fast. CloudZero has integrated with Amazon CloudWatch Container Insights for its strength as a secure and automated solution for sharing container metrics within AWS.
Over the last few months, I’ve been listening and involved in conversations about Kubernetes (k8s) and trying to identify the common topics that creates debate on whether it’s a “good” or “bad” idea. There are sensible points of view on both sides of the debate.
Looking back at my years working with infrastructure and going through it’s changes, I believe its time we start to rethink Operations because clearly this model of Ops as cluster or infrastructure admins does not scale. Developers will always out-demand their capacity to supply. Either your headcount is out of control or your ability to innovate and deliver is severely hamstrung. Operations becomes this interrupt-driven thing where we’re just fighting fires as they happen.
