Software is a product of the aggregate of decisions of past and present which directly impacts its future. Choosing an ecosystem like Kubernetes directly impacts your internal customers and the platforms that must be in place to support the workloads. Though Kubernetes is not immune from the human element; being 8 years old is similar to running a VM based workload in 2011.
As engineers change teams or organizations, intrinsic knowledge about the applications can disappear. More so, there might not be active development on Kubernetes workloads at some point. A duality of simplifying on and offboarding of Kubernetes applications and the ability to understand what is running and also validate what is running against policies are key.
In this session, learn about:
