Kubernetes learning paths by goal, role and experience

You can learn about Kubernetes through Kubernetes and Cloud Native Associate (KCNA) preparation without Linux terminal skills. The practical introductory Docker and Kubernetes workshops require those skills.

KCNA preparation requires basic understanding of servers, networks and operating systems, but no Kubernetes practice. For a practical introduction, the Linux introduction covers missing command line skills.

DevNinjas Kubernetes learning paths differ by goal: container and Kubernetes foundations, cluster operations, application development, security, automated delivery or exam preparation. Choose according to your responsibilities within the team and the knowledge you already have.

The path cards show the entry point, workshops and training days for each standard route. Missing foundations require additional preparation. If your goal is an exam credential, the certification guide helps you choose; exams are booked separately.

Certified Kubernetes Security Specialist (CKS) preparation requires administration practice, but no passed Certified Kubernetes Administrator (CKA) exam.

The CKS workshop requires confident use of Linux, TLS and YAML, plus experience with kubectl and kubeadm. For the CKS exam, you must previously have passed CKA; an expired CKA also qualifies. The Kubernetes certification guide explains exam admission.

You can book each workshop of a Kubernetes learning path separately. You do not need to commit to the entire route upfront. Start with a workshop whose prerequisites you meet and whose content you need.

The workshop schedule lists public training dates. The learning path itself does not reserve dates.

A Kubernetes learning path costs the sum of its workshop prices per person, plus VAT; additional preparation and optional topics cost extra. The displayed path price covers the standard route. Adding preparation in the learning path finder increases the displayed price accordingly.

Exams and exam vouchers are not included, even in exam preparation workshops. For a team, you can request a corporate training proposal; the displayed learning-path price is not a group price.

A Kubernetes learning path consists of separately bookable workshops; each public course runs on consecutive full training days. You can leave intervals between workshops.

The standard introductory Kubernetes route includes 9–10 training days; the cluster administration route includes 12. Additional preparation and your own practice take extra time. Agree the public dates and practice time with your employer. That plan determines the calendar duration, rather than a fixed number of study weeks.

To approve Kubernetes training, HR should know the learning goal, prerequisites, workshop scope, date, language and price per person. Agree any preparation and time away from work with the person responsible for technical requirements.

DevNinjas can provide a learning plan or agenda, issues invoices and documents participation with a PDF certificate of attendance and Open Badge. The workshop overview explains employer payment and the difference between attendance evidence and certification.

Access to the DevNinjas learning environment is limited to the booked course, excluding the period afterwards or between separate workshops. During the course, you use the browser-based DevNinjas Dojo without installing the exercise environment locally.

For independent practice outside booked courses, plan for an environment you can access separately. A learning path does not include continuous lab access between its individual workshops.

A practical Kubernetes learning route moves from Linux terminal foundations through container and Kubernetes fundamentals to operations practice and a suitable specialisation. The Zero-to-Hero learning path combines Docker or Podman with Kubernetes, followed by a choice between Helm and Kustomize.

This is a learning recommendation, not a mandatory course sequence: container knowledge helps when starting Kubernetes but is not a prerequisite. Later responsibilities can lead into operations, development, security or GitOps; existing skills determine your starting point.

To move into Platform Engineering, build on experience in DevOps, administration or development and develop operations and automated delivery skills. Platform teams build internal platforms with self-service for development teams; DevOps describes the broader approach to collaboration.

We do not offer a dedicated Platform Engineer learning path. For Kubernetes, we recommend Kubernetes Administrator for cluster operations or GitOps and Continuous Delivery for delivery, depending on your responsibilities. Infrastructure-as-code workshops complement these topics.