The presentation discusses the benefits of using managed Kubernetes clusters and how they can save time and money for developers and engineers.
- Managed Kubernetes clusters can simplify the deployment process and allow developers to focus on building their applications
- Managed services can take care of complex tasks such as scaling and security, freeing up time for engineers
- Using managed services may cost more in terms of cloud spend, but can save time and money in the long run
- It is not necessary to self-manage all aspects of a Kubernetes cluster, and using managed services for certain components can be a valid use case
The speaker shares their experience of unblocking themselves to build cool stuff by using managed services, and emphasizes that the choice of tools and methods should be based on what works best for the individual or team, rather than on the perceived bragging rights of self-managing clusters.
Seth will cover common misconceptions and dispel myths around the usage of managed Kubernetes services. Without focus on specific services in particular, more of a push towards acceptance of managed services, especially if you're an engineer or leader that is considering Kubernetes but don't know how to get started. When discussing a managed Kubernetes service, responses have range from “why?” or “managed services aren’t as powerful” or the all too common reference to "vendor lock in" - often leaving those on the receiving end with a feeling of being lesser. Viewers will walk away from this session with more acceptance of managed services, and realize that using a managed service doesn't make one a bad engineer. There are many benefits to be had adoption of Kubernetes, and it's not a contest to prove how much you can build. If you have a small team and want to use Kubernetes, then a managed service can be the first step or only step towards Kubernetes usage.