While Kubernetes comes with a number of benefits, it’s yet another piece of infrastructure that needs to be managed. Here, I’ll talk about three interesting ways that Honeycomb uses Honeycomb to get insight into our Kubernetes clusters. It’s worth calling out that we at Honeycomb use Amazon EKS to manage the control plane of our cluster, so this document will focus on monitoring Kubernetes as a consumer of a managed service.

Bridging the gap between development and operations has become essential for the cultural shifts seen in organizations today. DevOps allows these concepts to be brought together, creating an influential blend of cultural philosophies, practices, and technological instruments, facilitating a quicker delivery of products and services. Throughout this blog, I will explore how we should all be embracing DevOps to allow our organizations to compete in an ever-changing digital world.

Internal Developer Platforms have emerged as essential tools for streamlining processes and boosting productivity. As we find ourselves in the midst of 2023, the demand for robust developer platforms remains on the rise as organizations strive to find efficient solutions that expedite software delivery.

With the growing popularity of Kubernetes as a container orchestration platform powering the microservices revolution, comes greater complexity with managing, monitoring, and responding to incidents at scale. Challenges with real production environments include full visibility into your clusters and environment’s health, alongside real-time incident management and response.

Kubernetes is the gold standard for container orchestration at scale. While massive global companies like Google, Spotify, and Pinterest rely on Kubernetes to run their software in production, so do many small but mighty developer teams. (Full disclosure: Honeycomb joined the Kubernetes brigade last year, when we migrated some of our services.)

This week, I played at home as the rest of the DX team and I were at the AWS Summit London. 🇬🇧 The event was buzzing with excitement and overflowing with great talks and impressive exhibition stands. It didn't disappoint in terms of attendance either! Despite covering a wide range of subjects, I couldn't help but notice three super-hot tech trends that were everywhere throughout the day. So, without further ado, let's dive right in and explore these topics!

Kubernetes was designed by Google in 2014 and has been maintained by the Cloud Native Computing Foundation since 2015. It has become the de facto standard for running containers in production at scale, including in cloud environments such as AWS, Azure and Google Cloud. Kubernetes is a modern framework for managing and scaling containerized applications. There have been over 2.8 million contributions to Kubernetes made by companies.

When deploying a mission-critical Kubernetes infrastructure, the support you receive from your vendor is as important as the product. This is why we at D2iQ are especially pleased and proud that our D2iQ Customer Operations Team has won the Gold Stevie Award for Support Team of the Year for 2023. The American Business Awards, also known as the Stevie Awards, are billed as the “world’s premier business awards” and are judged by a panel of more than 200 industry experts.

Rising container usage has fueled a growing reliance on container orchestration systems such as Kubernetes, EKS, and ECS. As organizations increasingly opt to run these systems in the cloud, their cloud spend tends not only to grow but also to become more opaque due to the dynamic complexity of these environments. Typically, various services, teams, and products share cluster resources, and as nodes are added and removed, those resources continuously shift.

Running a Kubernetes cluster isn’t easy. With all the benefits come complexities and unknowns. In order to truly understand your Kubernetes cluster and all the resources running inside, you need access to the treasure trove of telemetry that Kubernetes provides. With the right tools, you can get access to all the events, logs, and metrics of all the nodes, pods, containers, etc. running in your cluster. So which tool should you choose?