Camp Fire Academy
Learning path
Complete UI/UX Masterclass UI/UX Design Foundations UI/UX Design Intermediate Advanced UX Strategy
Specialisations
Fintech & Banking UI/UX UI/UX with AI Training UX for Leaders Design Thinking Figma Training
Most requested
AI for Workplace Productivity Excel for Business Power BI & Business Intelligence Cybersecurity Awareness PDPA Compliance Data Protection Officer Browse the full catalogue →
For teams
Corporate & In-House Training LMS & Self-Paced Learning Events
Company
About Contact Verify Certificate WhatsApp

Containers & Kubernetes Basics

Kubernetes has a reputation for complexity that is partly deserved and partly a result of teams meeting it through a production incident rather than through a build. This programme goes the other way. Participants containerise an application, push it to a registry, deploy it to a cluster, expose it, configure it, give it storage, and then deliberately break it in the five ways that break real clusters, so the debugging is practised before it is needed.

Programme Agenda

Containers Before Kubernetes

What a container actually is, how it differs from a virtual machine, and why the distinction matters for resource use and startup time. Images, layers and the registry.

Building Images Properly

Writing a Dockerfile that produces a small, reproducible image. Multi-stage builds, base image selection, layer caching, and keeping secrets out of the image history.

Kubernetes Architecture

Control plane and nodes, the API server, the scheduler and the controller loop. The declarative model, and why describing desired state changes how you think about operations.

Pods, Deployments and ReplicaSets

Running the application. Rolling updates, rollbacks, replica counts, and the relationship between the three objects that trips up almost everyone at first.

Services, Ingress and Networking

Cluster-internal service discovery, service types, and getting traffic in from outside through an ingress controller. DNS inside the cluster.

Configuration, Secrets and Storage

ConfigMaps and Secrets, and the honest position on how secret a Kubernetes Secret is. Persistent volumes, claims and storage classes for workloads that need state.

Resources, Health and Scheduling

Requests and limits, what happens when a pod exceeds them, liveness and readiness probes, and why a missing readiness probe causes failed deployments to serve traffic.

Troubleshooting Clinic

The failure modes every team hits: ImagePullBackOff, CrashLoopBackOff, pending pods with no node, a service routing nowhere, and an out-of-memory kill. Each one induced and then diagnosed.

Learning Outcomes:
Explain what a container is and where it differs from a virtual machine
Write a Dockerfile producing a small reproducible image without embedded secrets
Describe the Kubernetes control loop and the declarative model
Deploy an application with rolling updates and roll it back
Expose a workload internally and externally through services and ingress
Manage configuration, secrets and persistent storage
Set resource requests, limits and health probes correctly
Diagnose the common cluster failure modes from the symptoms

Duration: 2 Days (16 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: Beginner
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included

Frequently Asked Questions

Developers, system administrators, DevOps engineers and technical leads whose organisation has adopted or is adopting containers. Also useful for platform teams inheriting a cluster somebody else built.

Command line comfort, basic Linux, and familiarity with how a web application is deployed. No prior container experience is needed.

A managed service or a local cluster depending on the delivery format. The material stays on standard Kubernetes objects rather than distribution-specific features, so it transfers to whatever you run.

They are introduced as the natural next steps with enough context to evaluate them, but the two days stay on core Kubernetes. Trying to add them properly would mean covering the fundamentals too thinly.

Yes, this programme is HRD Corp SBL-KHAS claimable. Our team can assist your HR department with the documentation required for the grant application.

Yes. Any programme can be booked as a team day. Everyone works the same brief together, so your people come away having built something and knowing each other better.

If you are claiming under HRD Corp, the session has to fall at least 14 days after your HRD Corp approval. If you are not claiming, the date is flexible and we work around your calendar.

Put them on the self-paced e-learning instead. Your team works through the modules on our LMS in their own time, sits the assessment, and earns the same certificate, so nobody has to clear a full day together.

More in Cloud, DevOps and Platform Engineering