Reach services across clouds with internal load balancers
One load balancer per service, or one Traefik routing by hostname. What each costs, why GKE pods need a masquerade fix, and how names resolve.
24 posts tagged “Kubernetes”.
One load balancer per service, or one Traefik routing by hostname. What each costs, why GKE pods need a masquerade fix, and how names resolve.
Build the tunnel between Google Cloud and Azure with BGP, advertise only what should cross, then test four layers until real traffic flows.
How an AI cloud fits together on Kubernetes, from what customers actually buy and the seven layers between datacenter and console to four products on one GPU pool and how tenants share it safely, the lessons AWS and Google learned about cells and control planes, and what changes with scale.
Declare images and charts in one manifest, package them into a single archive, carry it across, and serve it from a binary with no dependencies.
What it takes to run managed Kubernetes when you are the cloud, from hosted control planes, cells and etcd to networking, storage, upgrades and tenant isolation without cloud APIs, plus a version small enough to build on a laptop.
When a node, the control plane or the network fails, a structured workflow for finding the cause, and audit logs for reconstructing who did what.
A systematic way to debug Pods, Services and Deployments, then the two things that make debugging possible, metrics with Prometheus and Grafana and centralized logs.
Watch a running cluster for attacks with Falco, stop running containers from being changed with a read-only root filesystem, and record every API request with audit logs.
Everything between a commit and a running Pod can be attacked. Minimal and signed images, scanning in CI, locked-down pipelines and secrets, and checks at runtime.
Install it, point it at a cluster, and learn the handful of keys that replace most of the kubectl you type.
Enforce Pod Security Standards per namespace, limit what a container can do with AppArmor and seccomp, and isolate untrusted workloads with gVisor or Kata Containers.
Check a cluster against the CIS Kubernetes Benchmark with kube-bench, then control who can do what through the API server with authentication, RBAC and network policies.
When to put more than one container in a Pod, the three patterns for doing it, and init containers that run before your application starts.
A running container is not always a working one. Probes tell Kubernetes when to restart a container, when to send it traffic, and when to wait out a slow start.
Keep configuration out of your images with ConfigMaps, handle passwords and keys with Secrets, and know what base64 does and does not protect.
Upgrade a kubeadm cluster one minor version at a time, control plane first, then take and restore etcd snapshots, because etcd holds the cluster's entire state.
Prepare the nodes, install a container runtime and the Kubernetes packages, bootstrap the control plane, add a network plugin and join the workers. Then what each core component does.
A container loses its files when it stops. Volumes, PersistentVolumes, PersistentVolumeClaims and StorageClasses are how Kubernetes keeps data that has to outlive it.
Every Pod can reach every other Pod by default. Network policies cut that down to what you allow, starting from a default deny.
Give a changing set of Pods one stable address with a Service, choose the right Service type, and route outside traffic by host and path with Ingress.
Run applications that stay up with Deployments and the ReplicaSets behind them, and tasks that finish with Jobs and CronJobs.
What a Kubernetes object is, how a YAML manifest describes one, and the first two objects you will create, the Pod and the namespace.
Install kubectl, then start a local cluster with Minikube or Kind and check that it answers.
Why containers need something to run them in production, and the two halves of every cluster, the control plane that decides and the worker nodes that do the work.