Develop in complex, microservice-based environments
Quickly deploy and debug code changes using your existing development and staging Kubernetes clusters
In a micro-services, distributed based environments, when changing one service in a chain, developers need to either mock downstream dependencies or deploy into an existing environment with all actual services present.
Developing within these realistic environments allows developers to test their code under conditions that closely resemble what it will face in a production environment. Real-world variations in data, network latency, hardware, and external dependencies expose problems not apparent in mocked scenarios.
Developing code with actual services and conditions helps finding and fixing problems before reaching production as mocks simplify behavior and cannot replicate real-world complexity
Getting Started with K8s Init Containers
Kubernetes init containers provide a means of configuring an environment in K8s for an application to run that doesn’t require changing the application’s source code. In this post, we discuss how init containers work, when you would use one, and show an example in a sample app.
Getting Started with Argo Workflows
Argo Workflows is a K8s native workflow engine that allows you to run all kinds of workflows in Kubernetes by leveraging native resources, such as K8s Pods, to execute the individual steps of the workflow. Workflows can be kicked off in all kinds of ways, which – along with the enormous range of customizations possible – is what makes Argo Workflows such a versatile tool for running cloud-native workflows.