Operations | Monitoring | ITSM | DevOps | Cloud

The adoption and maturation of Kubernetes has been rapid, driven by organizations moving to cloud-native infrastructures to modernize and gain agility. The Kubernetes growth trajectory reached a climax in 2021 as The Cloud Native Computing Foundation (CNCF) declared it “the year Kubernetes crossed the chasm.” The CNCF Annual Survey 2021 found that 96% of organizations were using or evaluating Kubernetes.

If you are using Argo CD, you may be already familiar with how the Application CRD (Custom Resource Definition) object helps you logically group together your Kubernetes Manifests. The Application object is the atomic unit of work in Argo CD, and you should think of all your Kubernetes objects that are in an Application as a single entity. Applications are also autonomous. Meaning that, by design, one Application doesn’t know about the status or health of another Application.

In this Postman load testing tutorial, you’ll learn how to run a large scale load test in Kubernetes using your existing Postman collections. Because HTTP services don’t have a graphical user interface, it’s common to build collections of requests using Postman during the development process. These collections are useful for running quick functionality tests as you develop each endpoint.

Managing Kubernetes version upgrades can be a formidable undertaking. API versions are graduated, new features are added and existing behaviors are deprecated. Version upgrades may also impact applications needed by the Kubernetes platform; affecting services like pod networking or DNS resolution. At LogicMonitor, we ensure our Kubernetes version upgrades are successful through a process designed to instill collaboration and due diligence in a repeatable fashion.