geeked out on @kelseyhightower 's various recent podcasts on @kubernetesio . Much knowledge ingested. @kelseyhightower is an inspiring leader🙏. My top 10 takeaways / lessons ...
1. @kubernetesio will eventually disappear.
2. @kubernetesio will be consumed like linux distros
3. The container scheduler is just one of the manifestations of the API model - core runtime of @kubernetesio . #Kubernetes is NOT just for container schedulers. Entire platforms and vertical products can be built on it
4. @kubernetesio is rapidly iterating to its Rails moment. Nothing authoritative has arrived yet.
5. Hyper specialized PaaSs like K3s that specialize @kubernetesio for edge workloads or specific verticals will arrive soon. This will be a key part of the disappearance of @kubernetesio
6. Just like you need a licensed plumber to fix a water main leak - you will need a certified kubernetes administrators to go under hood when the @kubernetesio platform breaks
7. Don't be scared of @kubernetesio sys admins and developers simply have to do a mapping exercise to remap their mental models with the best practices of @kubernetesio
8. @KnativeProject + @apachekafka will be the substrate of the next set o platforms built on top of @kubernetesio Google cloud run sits between Kubernetes and knative. Much innovation is in the offing with Serverless platforms in the future
9. Control planes for clusters have to think out of the box. @kubernetesio Cluster management is not a solved problem
10. Be humble and start from first principles. Teach and mentor junior engineers. Be confident in your ability to assert positive change.
11. #gitops declarative > config as data model is about to take off in CI /C CD Tools and other forms of configuration and operations management
