In part 1 of this series on Kubernetes, we discussed how companies like VMware offer the necessary tools to launch, monitor, create and destroy virtual machines. In this post, we review how – much like virtual machines – containers need to be created, monitored, destroyed and relaunched to account for the health of the physical or virtual machines on which they run.

Kubernetes is the leading container-orchestration tool that was open-sourced in 2014 by Google and has helped engineers across the globe to significantly lower their cost of cloud computing ever since. Kubernetes also provides a resilient framework for deploying applications. Kubernetes management tools are quickly becoming essential to those that wish to monitor their containers on an ongoing basis, test, export and create intuitive dashboards.

Docker is a software platform that enables packaging an application into containers. These containers represent isolated environments that provide everything necessary to run the application. Dockerizing an application refers to packaging it in a Docker image to run in one or more containers. Dockerizing an application involves specifying everything needed to run the application in a Dockerfile and then using the file to build a specialized Docker image that can be shared to multiple machines.

In this three-part blog series, we examine the critical role Kubernetes plays in shaping the future of infrastructure, including the rise of containers and Kubernetes. The first in the series covers Next-Generation Application Development. The second covers the Next Frontier: Container Orchestration. And the third covers How Kubernetes Gets Work Done.

Matt and I are out in Los Angeles this week for KubeCon 2021 this week. At the GitOpsCon event Tuesday we were excited to attend this Kubernetes session: GitOps in the Real World: Opportunities for Developer Experience Improvement

In my previous blog post, CodeZero 301, I shared with you Part 3 of a four-part series directed at introducing you to the CodeZero platform and some of its useful tools and features for Kubernetes developers. Part 3 introduced you to the concepts behind Halyard, CodeZero’s next generation build and deployment feature that enables developers to ship code easier, faster, and with a higher level of quality.

A more agile and efficient infrastructure is key to realizing the cost savings and productivity gains businesses needed to succeed in today’s highly competitive market. Recent surveys by Roger Magoulas & Steve Sawyer, May 19, 2020, show that 88% of enterprises are currently using cloud in some form or another. This adoption is not surprising as clouds have been around now for several decades since Amazon Web Services (AWS) was launched in 2002.

In the last blog, we discussed the challenges in managing APIs at scale in a Kubernetes environment. We also discussed how deploying a Kubernetes Ingress Controller or an API gateway can help you address those challenges. In this blog, we will briefly touch upon some of the similarities and differences between an API gateway and Kubernetes Ingress. We will also discuss a unique approach offered by Kong for the end-to-end lifecycle API management (APIM) in Kubernetes.

KubeCon + CloudNativeCon North America is just around the corner. I’ve been looking forward to this event for a long time, especially since 2020 was virtual and it looks like there will be an in person option this year. This should be a great event and there are going to be a ton of awesome sessions. Last year was simply enormous with over 15K attendees who joined virtually.