Core concepts
Pods, Deployments, Services, Namespaces, ConfigMaps, Secrets, and labels form the basic vocabulary of Kubernetes.
Read detailsSecure static knowledge site
Kubernetes concepts, components, and secure cloud native operations.
A simple multi-page website explaining how Kubernetes coordinates containers, infrastructure, networking, storage, and security controls. The site itself remains static, private, dependency-free, and hardened for safe publication.
System overview
How Kubernetes works at a glance
1. You declare desired state
Teams describe workloads, services, policies, and configuration as Kubernetes API objects.
2. The control plane reconciles
Controllers compare desired state with actual cluster state and create or adjust resources.
3. Nodes run containers
Kubelet, the container runtime, networking, and storage integrations run application Pods reliably.
4. Security gates every step
Authentication, authorization, admission controls, policies, image hygiene, and network boundaries reduce risk.
Second-level pages
Explore the core topics
Architecture
The API server, etcd, scheduler, controllers, kubelet, kube-proxy, and runtime cooperate to maintain state.
Read detailsWorkloads
Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs map applications to the right execution pattern.
Read detailsNetworking
Services, DNS, Ingress, NetworkPolicy, and CNI plugins connect workloads while enforcing segmentation.
Read detailsStorage
Volumes, PersistentVolumes, PersistentVolumeClaims, StorageClasses, and CSI drivers attach durable storage.
Read detailsSecurity
RBAC, Pod Security Standards, admission control, image verification, Secrets handling, and runtime hardening.
Read detailsOperations
Observability, upgrades, backup, autoscaling, disaster recovery, and GitOps keep clusters maintainable.
Read detailsHighlighted outcomes
Cloud native, security focused, and agile
Cloud native foundation
Kubernetes supports declarative APIs, immutable infrastructure practices, service discovery, horizontal scaling, and portable deployment patterns across cloud and on-premises environments.
Security focused operations
Security is layered through identity, least privilege, network segmentation, hardened container settings, trusted images, secrets management, and continuous patching.
Container agility
Teams can ship smaller changes, roll out gradually, recover automatically, scale independently, and keep application packaging consistent from development to production.
Hardened static delivery
Site security model
No data collection
No forms, cookies, analytics, tracking pixels, local storage, session storage, third-party scripts, or outbound browser connections.
Strict CSP
Only same-origin CSS, JavaScript, and images are allowed. Object embedding, framing, remote connections, workers, and form posts are blocked.
Small attack surface
The site is static HTML, CSS, and minimal JavaScript for the mobile menu only. There is no backend, database, login, or API endpoint.
Deploy with headers
Use the included _headers or nginx-security.conf file to enforce browser protections at the hosting layer.