Corporate IT training for Docker, Kubernetes and DevOps

There are two ways to train your team in Docker, Kubernetes and DevOps: reserve an existing live workshop or ask us to build an agenda from relevant modules. Your team's work and current knowledge determine where we go deeper.

Live with a trainer · German or English · Remote or on site
Request a custom agenda

HOW TO GET STARTED

Which route suits your team?

If the subject and level are already clear, start with a workshop from our catalogue. If the training needs to cover several technologies, roles or workflows, start with the work your team needs to prepare for. We use that to develop a suitable agenda.

WORKSHOP FROM THE CATALOGUE

Enquire about an existing workshop

You know the subject and the level your team needs.

Choose the workshop, then we agree the date, delivery format, group size and areas of focus. Its existing agenda and technical structure remain intact.

HOW THE PROPOSAL TAKES SHAPE

  1. Choose a workshop

    Check the subject, level and agenda in the catalogue.

  2. Share the key details

    Tell us the format, group size and areas of focus.

  3. Review the proposal

    Check what is included and how the training will run.

TAILORED AGENDA

Ask us to combine relevant modules

Your training needs span several subjects or roles.

Tell us what the team needs to prepare for and what participants already know. We check which existing modules fit and which additional subjects we can teach well. We then propose an agenda for the time available.

You do not need to select the modules yourself.

PROPOSED PLAN

An agenda for your team

Modules and exercises arranged in a coherent sequence.

FROM THE TEAM'S WORK TO A PROPOSAL

  1. Describe the starting point

    Describe the team's tasks, roles and current level.

  2. Select the modules

    Review existing content and any additional subjects.

  3. Review the proposed plan

    Review the agenda, scope and delivery with us.

Request a custom agenda

What we clarify first

Subject · Level · Format · Group size

The enquiry is non-binding. After the initial discussion, you receive a proposal covering the details agreed with you.

Would you like to talk through the best starting point?

What should your team be able to do after the training?

We start with real tasks from the team's day-to-day work. Does the team need to review deployments with more confidence or troubleshoot faults systematically? Perhaps it needs shared criteria for technical decisions. Those tasks guide our choice of content and exercises.

FROM THE TEAM'S WORK TO THE AGENDA

4 STEPS

1 · Task

Which task should be easier for the team after training?

2 · Participants

Which roles are taking part, and what do they already know?

3 · Content

Which modules does the team need for that task?

4 · Exercises

How should the practical exercises build on one another?

Examples of useful training goals

A useful training goal names a task that the team can practise during the course.

  • Shared vocabulary

    Development and operations use the same terms when discussing workloads and incidents.

  • Handle routine tasks confidently

    Complete recurring tasks in the learning environment and troubleshoot faults systematically.

  • Justify decisions

    Compare technical options against shared criteria and explain the decision.

  • Know the limits

    Recognise what the team has practised and which questions can only be answered in its own production environment.

What we can adapt for your team

We adapt the examples, depth and pace to the tools, work and prior knowledge of the team. We include subjects outside the published catalogue only when we have the expertise to teach them and enough time to cover them properly.

  • Participants

    Roles, prior knowledge and shared tasks

  • Technology and exercises

    Technology stack, workflows and relevant practical examples

  • Delivery

    Format, language and group size

We would rather shorten the agenda than squeeze foundations and hands-on work into too little time.

WHAT WORKS AS TRAINING

Prior knowledge · Training goal · Time

Example: DevOps training from Docker build to GitOps

A platform team practises delivering a service from a Docker image through to a GitOps rollout. The technical steps link to existing workshops that cover parts of this workflow. What your team needs depends on its day-to-day work and prior knowledge.

ILLUSTRATIVE EXAMPLE · NOT A STANDARD PACKAGE

5 STEPS · BUILD TO GITOPS

Example task: build and deploy one service

Developers and platform engineers jointly maintain an internal service. During the training, both roles work on the same build and deployment process.

TEAM TASKS

Build an image · Maintain a Kubernetes deployment · Review a GitOps change

  1. Build a reproducible image

    The team writes Dockerfiles, builds images and examines how registries, networking and secure build settings work together.

    Docker Introduction · DW1

  2. Deploy and inspect the workload

    Using Kubernetes resources, the team configures the service, its networking and storage, and investigates rollout failures.

    Kubernetes Introduction · DW2Kubernetes Advanced · DW3

  3. Maintain deployment variants

    The team uses Helm or Kustomize to manage environment-specific differences within its existing workflow.

    Helm Introduction · DW9Kustomize Introduction · DW22

  4. Deploy a change through GitOps

    With Argo CD or Flux CD, the team deploys an approved change from Git and follows its sync status.

    Argo CD Introduction · DW27Flux CD Introduction · DW28

  5. Connect the workflow in the Dojo

    In the Dojo, the team brings the build, deployment and GitOps steps together. Access is limited to the booked training, and production remains separate.

    Build, deployment & GitOps in the course lab

ROLE-SPECIFIC FOCUS

How does the focus change by role?

Everyone works on the same service while taking on tasks relevant to their role.

Development

Developers build the image, maintain the workload configuration and investigate failed builds or rollouts.

Platform Engineering

Platform engineers define deployment standards, set access boundaries and investigate cluster faults.

Technical Leadership

Technical leads assess Helm or Kustomize, clarify ownership and agree the team's change process.

Not every team needs all five steps. We remove or expand modules so the exercises fit the time agreed for the training.

PLANNED AFTER NEEDS ASSESSMENT

Learning goal · Prerequisites · Time frame

Workshop selection

Which workshops could be a starting point for your corporate training?

The selection covers Linux, Git and containers as well as Kubernetes, GitOps, observability and certification preparation. Entries showing duration and level take you to the in-house inquiry for that workshop; the other topics can be planned as corporate training.

Workshop topics at a glance
6 Subject areas · selected workshops

The level shown is the starting point; we adapt the depth to your team.

5 Workshops

Foundations, containers & version control

Linux, Git and containers provide a shared foundation for development and operations.

  • DW18Introduction to LinuxTerminal, Bash and ZSH, shell scripting, networking and SSH.3 Days
  • DW19Introduction to Git for TeamsGit workflows with branches, conflict resolution and collaboration in the team.3 Days
  • DW26Introduction to Git and GitLabGit and GitLab with branches, merge requests, reviews and project management.3 Days
  • DW1Introduction to DockerContainer CLI, Dockerfiles, multi-stage builds and Docker Compose.2 Days
  • DW8Introduction to PodmanRootless containers, Podman Compose, pods and Kubernetes integration.3 Days
6 Workshops

Kubernetes & platform operations

Kubernetes fundamentals, platform variants, cluster operations and communication between services.

  • DW2Introduction to KubernetesPods, deployments, storage and deployment strategies with kubectl, K9s and Helm.3 Days
  • DW4Docker and Kubernetes EssentialsFrom containers and images to Kubernetes deployments, self-healing and storage.5 Days
  • DW3Advanced KubernetesStatefulSets, RBAC, autoscaling and Kubernetes monitoring.2 Days
  • DW13Introduction to Red Hat OpenShiftOpenShift web console, builds, routes, operators and security context constraints.3 Days
  • DW12Introduction to RancherRancher, RKE2, Fleet GitOps, Longhorn, backup and monitoring.3 Days
  • DW16Introduction to Istio and Service MeshIstio traffic management, mTLS, ambient mesh and observability.3 Days
  • DW56Introduction to HashiCorp VaultCentral secrets management with Vault, Kubernetes integration and edition selection.Plannable as corporate training
  • DW57Introduction to OpenBaoOpenBao, self-hosted secrets management, high availability and migration from Vault.Plannable as corporate training
  • DW58Introduction to CrossplaneCloud resources through Kubernetes APIs, compositions and self-service with Crossplane.Plannable as corporate training
5 Workshops

Delivery & GitOps

CI/CD, packaging and declarative delivery within GitOps workflows.

  • DW14Introduction to GitLab CI/CDGitLab pipelines, runners, caching, scanning and review apps.2 Days
  • DW9Introduction to Helm for KubernetesDeveloping, testing and publishing Helm charts and integrating them into GitOps.3 Days
  • DW22Introduction to KustomizeBases, overlays, patches, generators and components with Kustomize.2 Days
  • DW27Introduction to Argo CDArgo CD with Helm, Kustomize, ApplicationSets and Argo Rollouts.3 Days
  • DW28Introduction to Flux CDFlux GitOps with Kustomize, Helm, OCI, secrets and monitoring.3 Days
  • DW50Introduction to KargoKargo, version promotion across environments, verification and integration with Argo CD.Plannable as corporate training
  • DW51Introduction to TektonKubernetes-native pipelines with Tekton, building and triggering CI/CD workflows.Plannable as corporate training
4 Workshops

Observability, IaC & Automation

Monitoring, Infrastructure as Code and automation for platform operations.

  • DW10Kubernetes Monitoring and ObservabilityPrometheus, Grafana and Loki: queries, alerting, SLOs and performance tuning.4 Days
  • DW20Introduction to TerraformHCL, state management, modules, CI/CD and security scanning.3 Days
  • DW21Introduction to OpenTofuHCL, state encryption, modules, CI/CD and Terraform migration.3 Days
  • DW23Introduction to AnsibleInventories, playbooks, Jinja2, roles and Ansible Vault.3 Days
  • DW53Terraform AdvancedTerraform, HashiCorp platform, Stacks, policy checks and governance for larger teams.Plannable as corporate training
  • DW54OpenTofu AdvancedOpenTofu, self-hosting, module distribution, provider mirrors and operation in isolated networks.Plannable as corporate training
  • DW55Ansible AdvancedAnsible collections, testing with Molecule, AWX and Event-Driven Ansible.Plannable as corporate training
3 Workshops

Cloud-native development

Go and Rust fundamentals, plus developing Kubernetes operators.

  • DW17Introduction to Go ProgrammingGo fundamentals, goroutines, channels, an HTTP server and a CLI tool.3 Days
  • DW15Develop Kubernetes Operators with GoKubernetes operators with Go, Kubebuilder, CRDs, webhooks and testing.3 Days
  • DW29Introduction to RustOwnership, borrowing, Tokio, a CLI tool and a web server with Rust.4 Days
  • DW52Introduction to BackstageBackstage, developer portal, software catalogue, templates and documentation for your team.Plannable as corporate training
5 Workshops

Certification preparation

Preparation for KCNA, CKAD, CKA, KCSA and CKS, based on each exam's format.

  • DW24KCNA Exam PreparationKCNA: Kubernetes architecture, orchestration, cloud native and a mock exam.2 Days
  • DW5CKAD Exam PreparationCKAD: pod design, services, deployment strategies and self-healing.3 Days
  • DW6CKA Exam PreparationCKA: cluster setup, troubleshooting, etcd, networking and RBAC.4 Days
  • DW25KCSA Exam PreparationKCSA: security fundamentals, cluster hardening, compliance, Falco and OPA.3 Days
  • DW7CKS Exam PreparationCKS: cluster hardening, supply chain security and runtime security.4 Days
  • DW49Preparation for the Linux Foundation Certified System Administrator (LFCS) ExamLFCS: Linux system administration, users, services, networking, storage and practical troubleshooting.Plannable as corporate training
  • DW41Preparation for the Prometheus Certified Associate (PCA) ExamPCA: Prometheus architecture, PromQL, instrumentation, service discovery, alerting and monitoring.Plannable as corporate training

About this selection

Where a duration is shown, the duration and level refer to the complete public workshop; the other topics do not yet have a fixed duration. For combined modules, we define the content and duration anew.

AGENDA AFTER NEEDS ASSESSMENT

Can't see the right topic?

Tell us which task your team needs to practise.

We check which existing modules fit and how much can reasonably be covered in the available time.

Request a custom agendaView the full workshop cataloguePlan your team's topic sequence

FROM ENQUIRY TO TRAINING

How we prepare your corporate training

We start by discussing the team's work and current knowledge. We use that to prepare the agenda and proposal. Once these are agreed, we prepare the exercises and learning environment. After the live training, we gather feedback and record the next practice steps.

PATH AChoose a workshop and add the details

PATH BDescribe the work and receive a proposed agenda

FROM THEREAgenda, proposal and delivery

5 STEPS FROM THE FIRST CONVERSATION TO FOLLOW-UP

WHO DOES WHAT, AND WHAT IS DECIDED NEXT?

  1. Clarify the team's work and current level

    You tell us what the team works on, what it already knows and which questions remain. You also share the group size, language, format and preferred dates.

    OUTCOME

    We know what the training needs to cover and for whom.

  2. Prepare the agenda and proposal

    We propose the modules, exercise sequence and delivery format. The proposal lists the services, pricing factors and assumptions behind the plan.

    OUTCOME

    You can see what is included before placing the order.

  3. Prepare training and learning environment

    We select the trainer and prepare the exercises and learning environment. We check browser access, VPN or proxy requirements and suitable internal examples before the training date.

    OUTCOME

    Exercises, lab access and technical requirements are confirmed.

  4. Train together live

    The trainer explains the agreed topics and supports the team through the exercises. The trainer addresses questions as they arise during the exercises.

    OUTCOME

    The team has worked through the agreed topics in the lab.

  5. Review the training

    We gather feedback, compile the agreed materials and record the next practice steps.

    OUTCOME

    The team knows what to practise next.

THE PROPOSAL COVERS

Agenda and duration · format, language and group size · exercises and learning environment · preparation, travel and pricing factors · assumptions and agreed follow-up

Enquire about team training

If you need production access, architecture work or implementation, we agree a separate consulting brief. Travel, room and network requirements are included in the proposal where relevant.

How can your team practise without opening up the production system?

Your team can use the browser-based DevNinjas Dojo for practical exercises when it is included in the proposal. Production stays separate. Before the training, we check browser access, VPN, proxy and firewall requirements. We use internal examples only in prepared or anonymised form.

What is DevNinjas Dojo Workshop Access?

In the Dojo, the team works in prepared browser workspaces.

The trainer guides the exercises live.

Does the training need access to your production system?

No. Your production system remains separate.

We use internal workflows or examples only in prepared or anonymised form. Confidential data does not belong in the learning environment.

Not required: production access, credentials or confidential production data.

Technical check before training

We check browser access and any required VPN, proxy or firewall permissions with you. Only this check can show whether the planned environment will work in your network.

Access is limited to the booked training.

Period stated in the proposal · not a public or standalone learning platform · not for production use

Which delivery format suits your team?

You can book the training remotely, on-site or in several blocks. We agree the language and group size in the proposal.

Remote
Live with a trainer in the agreed learning environment, with participants able to join from different locations.
On-site
Live at your agreed location. The proposal records travel, room and equipment requirements.
In phases
Several coordinated training blocks work well when your team needs time to apply what it has learnt between sessions.

Shared arrangements

Language
German or English by agreement.
Group size
For intensive hands-on work, we recommend groups of up to eight participants. For larger groups, we agree a different teaching approach.

How is corporate IT training priced?

We can calculate the price once the content, duration and format are clear. Preparation and group size also matter. Before you order, the proposal shows what is included and which details the price is based on.

HOW THE PROPOSAL IS BUILT

CONTENT · TEAM · DELIVERY

What goes into the calculation

SIX FACTORS AT A GLANCE

Content and duration

  • Training days and schedule

    How much time the agenda needs and whether it is spread across several dates.

  • Selection and preparation

    Which modules can be reused, adapted or prepared for your team.

Group and trainer

  • Participants and support

    Group size, prior experience and the amount of hands-on work.

  • Subject expertise

    The trainer and any additional expertise needed for the topics.

Format and technology

  • Remote or on site

    Delivery format, travel, rooms and scheduling.

  • Lab and infrastructure

    The agreed learning environment plus network and technical checks.

ITEMISED IN THE PROPOSAL

Agenda · Duration · Delivery · Preparation · Learning environment · Travel · Pricing factors · Assumptions

WHY IS THERE NO FIXED PRICE HERE?

An existing Docker workshop already has an agenda. Training built from several modules for different roles needs separate planning and preparation. That is why one published price would be misleading.

TRAINING OR IMPLEMENTATION?

PRODUCTION WORK REQUIRES A SEPARATE BRIEF

When does training become a consulting engagement?

During training, the trainer explains approaches and supports your team through exercises in a learning environment. If DevNinjas is asked to analyse your system, design an architecture or work in production, that is consulting. Access, responsibilities and deliverables are agreed separately for that work.

COMPARISON BY CRITERION

CORPORATE TRAINING

CONSULTING & IMPLEMENTATION

GOAL
CORPORATE TRAINING: The team builds knowledge and practises repeatable tasks.
CONSULTING & IMPLEMENTATION: Work on a specific system or project.
STARTING POINT
CORPORATE TRAINING: Tasks, current knowledge and the agreed agenda.
CONSULTING & IMPLEMENTATION: Your systems and a specific project brief.
WAY OF WORKING
CORPORATE TRAINING: Your team works in the lab; the trainer explains and supports.
CONSULTING & IMPLEMENTATION: DevNinjas analyses the system and carries out the agreed design or implementation work.
ACCESS & RESPONSIBILITY
CORPORATE TRAINING: The training takes place without production access.
CONSULTING & IMPLEMENTATION: Access, responsibilities and safeguards are agreed separately.

We offer separate consulting services for work on production systems.

NEXT STEP

Discuss your training and proposal

Start with the topic, team size and preferred dates.

Request a custom agenda

Feedback from the Docker & Kubernetes Workshop (DW4)

PARTICIPANT FEEDBACK · DOCKER & KUBERNETES · DW4

“Adjusting the workshop focus to suit the participants' requests was no problem. The instructor shared valuable practical experience and readily answered more specialised questions.”

S. Kaiserforcont business technology GmbH
View the Docker & Kubernetes Bundle (DW4)
Trainer selectionWe select the trainer to suit the subject, date and agreed scope.
SourceOne participant comment on DW4, not a case study of custom corporate training.

Frequently asked questions about corporate IT training

Answers about choosing and planning training, group size, technical requirements and the proposal.

Your contact for corporate training

Vincent Sturm

Key Account Manager

Not sure whether an existing workshop or a tailored agenda is the better fit? Vincent can discuss the subject, participants and possible dates with you and help you choose.

vincent@devninjas.io
+49 221 9865099-4
WhatsApp chat

Do we need a finished agenda to enquire about corporate training?

You do not need a finished agenda to enquire about corporate training with DevNinjas. The subject or learning goal, approximate group size and possible dates are enough to start. Prior knowledge, language and format help us select the course. For an existing workshop without adaptations, allow about two to four weeks from enquiry to a possible date. This is an estimate, not a date commitment. The agreed agenda is recorded in the proposal before ordering.

Can you adapt corporate training to our technology stack and workflows?

Corporate training can be adapted to your team's technology stack and workflows. If the subject and level are clear, choose a catalogue workshop and enquire about running it exclusively for your team.

If the training needs to cover several areas of work, we propose a tailored agenda using relevant modules. We adapt the exercises to your work. We only add subjects when we have the expertise to teach them and enough time for practice.

Do corporate training participants need the same level of prior knowledge?

Corporate training participants do not need the same level of prior knowledge. Before planning, we ask what your team does and what each participant already knows. We adapt the pace and exercises accordingly. If the differences are too wide for one agenda, we suggest separate training days or groups.

Can corporate training use our own examples without production access?

Your own examples can be prepared or anonymised for DevNinjas corporate training without access to your production systems. We do not need credentials or confidential production data for this. An NDA is available on request; your material stays internal and is not reused. The included DevNinjas Dojo gives each participant their own browser-based exercise resources. System analysis, architecture design and production work require a separate consulting engagement.

What group size works well for hands-on corporate training?

For hands-on corporate training, DevNinjas recommends about eight participants; there is no minimum group size. Larger groups are possible and may require additional training days. Separate groups can make sense when prior knowledge varies widely. We record the agreed group size and planned training days in the proposal before you place an order.

Can corporate training run remotely, on site or in several blocks?

DevNinjas corporate training can run remotely, on site or in several blocks. Remote sessions use Microsoft Teams, Zoom, Google Meet or DevNinjas' self-hosted system. For on-site training, travel is billed at actual cost and stated in the proposal. Several blocks leave time between sessions to apply what participants have learnt. Training can take place in German or English.

Which network requirements do we check before corporate training?

For corporate training, DevNinjas checks browser access to the planned learning environment with you one to two weeks before the course. Your IT team clarifies any necessary VPN, proxy or firewall permissions. If access fails, we work with your IT team on a solution, such as suitable permissions, another network or different devices. The specific approach depends on your technical constraints.

What determines the corporate training price, and when is it invoiced?

The price of DevNinjas corporate training depends on group size, duration and preparation effort; the invoice is issued after the training. Before ordering, you receive a proposal stating the individual price and included services. The agreed agenda describes the training scope. This lets you review the content, time commitment and proposal together for your internal approval.

Plan the right training for your team

Choose the starting point that is easiest for you. We will work through the remaining details in a conversation.

CUSTOM AGENDA

Request a custom agenda

Tell us what your team needs to handle better after the training. We will review the relevant modules and propose a realistic agenda.

A subject, team size and preferred dates are enough to start.

Request a custom agenda

EXISTING WORKSHOP

Request a workshop for your team

Already know the subject and level? Choose the relevant workshop and tell us the team size, preferred format and possible dates.

The published agenda remains the basis for the training.

Still unsure? Vincent can help you choose the best starting point.