Automating Your Kubernetes Environments With Custom Resources
Let's be honest — having a local development that resembles anything close to production is on the same level as catching Bigfoot. Between differences in networks, storage types and computer resources, it's pretty much impossible. But wasn't portability and ubiquitous cluster config in the Kubernetes brochure?
In this session, we are going to look at how an operations team running a Kubernetes-based platform can use custom resources to offer their consumers a straightforward experience between environments.
First, we will take inventory of the backing services available to development teams. Then we're going to define the stack as a custom resource definition. Along the way, there will be caveats, so we will also be discussing when it makes sense to up your game with aggregated APIs. With this new definition in hand, we're going to add realistic features a consumer would need to run in limited computer environments (like their desktop), in a staging environment and at scale. The result of this work will be a contract that an Operations team shares with a Development team, where the Ops domain knowledge is built-in for the Devs to consume.
Destination: Automation is a free, digital event exploring ways organizations can embrace automation to make their applications and underlying tech stacks more efficient, secure and resilient.