Danielle Burrow and Munjal Munshi contributed to this blog post. Every modern enterprise is building applications to generate revenue, connect people and systems, and automate processes. Modern applications, architected to take advantage of the flexibility and efficiencies of the cloud, are projected by IDC to surpass traditional apps by 2024.

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.

The biggest question facing many businesses today is how to improve the efficiency and agility of their application delivery processes. Along the journey to infrastructure modernization, do they continue to maintain applications as-is, or do they need to be migrated, upgraded or replaced? This blog attempts to answer some of these questions. Take any popular enterprise app, like your Oracle business suite, or even a custom-built application, and it will typically follow a three-tier architecture.

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.

One of the great things about GitFlow is that it makes parallel development very easy by isolating new development from finished work. New development, such as features, is done in feature branches and is only merged back into the main body of code when developers have validated the feature and the code is ready for release. For most development teams, feature validation happens in a staging branch coupled with a single testing environment.