This document provides an overview of how to become proficient in Kubernetes. It discusses how Kubernetes skills are in high demand but difficult to obtain experience in. It suggests identifying existing technical skills that relate to Kubernetes concepts like containers and microservices. It recommends practicing expansion learning by focusing on small gaps in knowledge. Adopting small daily habits like using containers as the default command line can help build skills. Non-technical "DevOps" skills like communication, problem solving and teaching are also important for Kubernetes roles. Certifications may help get initial opportunities but cultural adoption of Kubernetes requires patience and leadership. The profile of a successful Kubernetes practitioner can vary widely.
2. Agenda
◻ VP of Engineering @ ReactiveOps
◻ Background in operations
◻ DevOps and engineering culture enthusiast
◻ Manage a team of 15 SREs for 25+ production
Kubernetes infrastructures
◻ Hiring manager focused on Kubernetes talent
github.com/sairez
2
Hi! I’m Sarah
@szelechoski @sarahz
3. Agenda
☐ Hard to find
○ This is all very new (yes, really)
○ No real “pipeline”
○ Rare opportunities to learn on the job
☐ Very valuable right now
○ Market is hot. High demand talent
○ Companies are piling on responsibility
○ Can justify high salaries
3
Kubernetes Talent in Today’s Market
4. Agenda
☐ Folks out there is all different niches of technology that have strong, relevant skills
○ Network engineers, operations folks, developers, educators
☐ Need Chances to
○ Apply skills to a new syntax
○ Learn on the job
○ Be supported by culture and executive buy-in
☐ Raw material is
○ undervalued
○ not well understood
4
Kubernetes Potential in Today’s Market
5. “People are so eager to learn because they see it’s a
growing tool/skillset, but also don’t know how to get
the experience at their current work.”
6. Agenda
☐ Identify technical skills and experience you currently have that are relevant/different
☐ Practice expansion learning
☐ Change small habits in your daily workflow
☐ Understand non-technical skills which are valuable in the transition
6
Transitioning existing skills into the Cloud Native/Kubernetes Space
12. Agenda
☐ Identify topic you wish to understand
☐ Which current skills
○ Relevant
○ As close as possible
☐ Focus on the delta
☐ , yet
☐ #daily30
12
Expand your knowledge
13. Agenda
➢ I would love to understand CI/CD.
➢ I know how to test and deploy an application manually.
➢ What is the difference between integration and testing?
➢ What is the difference between deployment and continuous
deployment?
13
Example
15. Agenda
☐ Choose a skill you would like to learn
☐ Identify the first step in that learning process
☐ Design a small change to your daily workflow to integrate this skill
☐ Practice this small habit every day
☐ Note the sticking points and lessons learned
☐ Integrate back in to your expansion learning
15
Practice Daily
16. Agenda
➢ I would love to be able to learn about containers/Docker
➢ The first step is understanding what a container is and how to use it
➢ I will build a basic container and use it as my command line
➢ This will be my command line for 30 days
➢ I will keep a log of the lessons I learn
16
Example
19. Agenda
☐ Problem Solving
☐ Ability to Learn and Teach
☐ Ownership/Integrity
☐ Communication
☐ Conflict Resolution
☐ Decision Making
☐ Continuous Improvement Mindset
19
Often More Important than Technical Skills
21. Agenda
☐ Yes and No
☐ Some certifications mean more than others
○ Certified Kubernetes
○ AWS/GCP
☐ It will help you get that first hook
☐ It will help make your last argument
21
Do They Mean Anything?
23. Agenda
☐ Kubernetes adoption requires
○ Cultural change
○ Manager/Executive/Org buy-in
☐ As a practitioner
○ You will have to fight the good fight
○ Be patient, kind and compassionate for change
○ Shoulder a lot of responsibility
○ Are often lonely
23
Kubernetes Adoption Requires Change
25. Agenda
☐ It’s a spectrum!
○ Developer
○ Systems
○ Operator
○ Educator
☐ Kubernetes is a shared language intended to change the way we work
☐ Apply what you know to new problems
☐ Bring your own experience and make it valuable
25
What does a Kubernetes Practitioner Look Like