Kubernetes knowledge transfer from learners to their colleagues

We offer private, instructor-led training for engineers who have begun learning Kubernetes and need to help colleagues develop the same foundation.

The original learners can recognize resources and repeat some exercises. Guiding another engineer also requires an explanation of the mechanism, a clear starting state, and a way to detect misunderstanding.

LearnKube uses a reference workload and bounded teach-back exercises. Participants practice the task, explain its behavior, and guide a colleague through a variation without taking over the work.

Discuss your team's training

Learning in practice

Hands-on learning and the skills engineers take back to work.

Preview: course-wide figures are not yet available.

Hands-on learning
60%
Of instruction time spent on labs and challenges.
Troubleshooting confidence
86%
Of respondents report greater confidence diagnosing Kubernetes problems.
Relevant to your work
92%
Of respondents say the course addressed their engineering responsibilities.
Skills put into practice
95%
Of respondents applied their new skills at work within 90 days.

Prepare to explain and demonstrate one technical task

Orient to the teaching task by revisiting the Kubernetes concepts behind a familiar exercise, so the learner knows which prerequisite a colleague needs.
Practice a guided demonstration with explicit starting conditions and expected observations, so the learner can explain the action instead of only reproduce its steps.
Demonstrate a teach-back through a changed example and questions about its result, so both engineers can identify remaining gaps or requests for support.
Transfer the technical reasoning through personal explanations, repeatable practice, and appropriate references, so a colleague can revisit the task without depending on the original demonstration.

Transfer the model behind the working example

A learner who remembers a successful exercise still needs to explain why it worked before guiding a colleague. Kubernetes controllers and owner references make a workload-replacement example observable. The workshop uses that relationship to connect a prediction, a controlled change, and the resulting resources, then asks another learner to account for the outcome.

I ask the original learner to predict the result before a colleague makes a change. An explanation of an unexpected Pod replacement reveals more about transfer than a command sequence copied without understanding.
— Daniele Polencic, LearnKube founder and Kubernetes instructor

Role milestone	Required knowledge	Practice/check
Prepare a demonstration	Starting state and prerequisites	Explain the initial resources
Predict a replacement	Controllers and object ownership	Compare prediction with outcome
Guide a colleague	Observable steps and questions	Let the colleague explain
Support later repetition	References and setup assumptions	Record a repeatable example

Case Study: MedImpact

MedImpact received private Kubernetes training with different depth for infrastructure/security and development roles. After delivery, the team began arranging cross-training by the original learners and asked about access to the workshop labs.

That follow-up identified a further learning need: helping participants explain and pass on what they understood. The proposed agenda below adds practice for that next step.

A recommended four-day path toward peer cross-training

This proposed agenda revisits the concepts participants need to explain and adds short technical teach-backs. Learners prepare their own explanations and practice notes, supported by appropriate references and the resources available to them.

Day 1

Reconstruct and explain a guided deployment

We revisit images, workloads, Services, probes, and rollout behavior through a familiar sample. Each learner identifies the prerequisites and explains the expected result before demonstrating the task.

Hands-on exercises

Prepare a supported deployment and explain its starting configuration and health checks.
Ask a colleague to predict the effect of a small release change, then compare the observed result.

Day 2

Explain relationships without taking over

We use Helm and compare Kustomize to connect input values to resources. Architecture and controller examples show who acts on desired state and how a replacement relates to its owner.

Hands-on exercises

Guide a colleague through a configuration variation while the colleague explains each decision.
Trace a replacement Pod through its owner references and compare both engineers' explanations.

Day 3

Use a problem to check the explanation

We trace networking, ingress, policy, and placement through the same service. Scheduling and service mesh discussions identify when the demonstration needs an additional concept or a specialist's input.

Hands-on exercises

Prepare a bounded connectivity fault and ask a colleague to choose the next observation.
Explain a placement constraint without supplying the final correction before the colleague has reasoned through it.

Day 4

Combine the demonstration and plan continued use

We connect state, configuration, scaling signals, and access to the selected role task. Learners deliver a short technical teach-back and identify which parts still require review or guided repetition.

Hands-on exercises

Demonstrate a state or permission scenario and ask a colleague to explain the result.
Record the setup, expected observations, and public references for a repeat practice session.

Your original learners' knowledge, colleagues' next tasks, and plans for cross-training can shape the agenda. Get in touch to tailor the learning path to your team.

Check the colleague's model, not only the demonstration

When a learner says that the node recreated a deleted Pod, the instructor can trace the workload's controller and owner references. The colleague then explains the distinction, making the teach-back a check of understanding rather than another completed command sequence.

Tomislav described a resource that helped him revisit the teaching:

The textual summary for each topic (always above the challenges/labs) helped a lot to recap the presentations after each day.
— Tomislav, Data Engineer at Alexander Thamm.

Start with what the first cohort needs to explain

Tell us what the original learners understand, which tasks their colleagues need next, and what practice resources are available. We will recommend a technical focus and checks for the knowledge you want to transfer.

Discuss your team's training