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.

CodeZero’s mission is to help Developers be 10x more productive on Kubernetes, which is why we’re thrilled to announce that we’ve joined the Equinix Metal Partner Ecosystem alongside a huge roster of other Kubernetes and Hybrid-Multi Cloud projects and companies. We’ll admit that we didn’t know a great deal about Equinix until we met the folks at Equinix Metal and learned of Equinix’s 20 year history of creating neutral partner led ecosystems.

Despite tremendous benefits, 47% of the Kubernetes community reports a steep learning curve as a barrier to adoption according to a recent survey of 1000 Developers by Civo.com. So when our team started out on Kubernetes, we went out looking for online resources to learn from and we have been following Viktor Farcic for well over a year now. Viktor is the author of the DevOps Paradox podcast and has a weekly video series called the DevOps Toolkit by Viktor Farcic on YouTube.

In my previous blog post, CodeZero 201, I shared with you Part 2 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 2 discussed two incredibly handy features for working with Kubernetes called Teleport and Intercept.

Kubernetes continues to lead the container orchestration charge. In fact, according to the latest CNCF survey, 83% of respondents said they were using Kubernetes in production. Kubernetes provides you with key features such as self-healing capabilities, automated rollouts and rollbacks, automated scheduling, scaling, and infrastructure abstraction. This provides a truly extensible, highly available and infrastructure-agnostic environment to deploy all your modern microservices-based applications.

In my previous blog post, CodeZero 101, I shared with you Part 1 of a four-part series directed at introducing you to the CodeZero platform and some of its useful tools and features for Kubernetes developers. While Part 1 focused on laying a technology foundation, this second post gets into CodeZero itself, and introduces two incredibly handy features called Teleport and Intercept. Teleport allows developers to develop and debug their code locally as though they are inside the cluster.