What to expect
Harden the cluster and master its networking layer over five hands-on days: CIS benchmarks, Cilium, Gateway API traffic management, supply-chain security, and NetworkPolicy, all running on your own kind cluster.
Harden the cluster and master its networking layer: CIS benchmarks, Cilium, Gateway API traffic management, supply-chain security, and NetworkPolicy - all on your own kind cluster.

Harden the cluster and master its networking layer over five hands-on days: CIS benchmarks, Cilium, Gateway API traffic management, supply-chain security, and NetworkPolicy, all running on your own kind cluster.
Lots of practical, hands-on teaching. Theory shows up only when you need it to unblock the next exercise.
Mostly hands-on. Most of the session is spent building real labs and real pipelines, not watching slides.
Your own cluster, not a shared sandbox. Every participant runs a real multi-node kind cluster on their own VM, so what gets built in the room is what ships on Monday.
Small enough that everyone drives. Groups of 4-12, so every attendee gets keyboard time.
You keep the runbook. Labs, scripts, and reference material go home with your team as the start of your own documentation, not a one-off slide deck.
Tell us a bit about your team and we'll get back to you to schedule Kubernetes Security and Networking.

Principal Engineer
“Networking and security get bolted on after an incident, not designed in from day one. We spend a full week doing both together, because a NetworkPolicy nobody understands is worse than no NetworkPolicy at all.”
Kubernetes Security and Networking
Harden the cluster and master its networking layer: CIS benchmarks, Cilium, Gateway API traffic management, supply-chain security, and NetworkPolicy - all on your own kind cluster.
Go from container basics to a production-shaped Kubernetes cluster: architecture, workloads, networking, storage, troubleshooting, and observability - all on your own kind cluster.
Run production workloads on EKS: networking, autoscaling, GitOps deployment, and the operational habits that keep clusters calm.
Run and ship on a cluster you maintain yourself: kubeadm upgrades, etcd backup and restore, GitOps with ArgoCD or Flux, and progressive delivery - all on your own kind cluster.