jongminchungtech
BlogSeriesShowcase
KO
Kubernetes

Cilium Gateway API

  • Cilium Gateway API Part 1: Choosing an External Entry Point
  • Cilium Gateway API Part 2: An External Load Balancer in Front
  • Cilium Gateway API Part 3: Boundaries in a Multi-Control-Plane Cluster
  • Cilium Gateway API Part 4: Per-Node Cloud Public IPs Without an LB

Operations and Reliability

  • Distributed Failure Handling Part 3: How OpenStack and Kubernetes Converge After Failure
K8s

Kubernetes

Design and operational guidance for Kubernetes networking, Cilium Gateway API, and distributed control loops.

Cilium Gateway API

Cilium Gateway API Part 1: Choosing an External Entry PointUnderstand the Cilium Gateway API data path and choose between LoadBalancer, NodePort, and hostNetwork exposure.Cilium Gateway API Part 2: An External Load Balancer in FrontCompare LoadBalancer, NodePort, and hostNetwork paths from an existing external load balancer to Cilium Gateway API.Cilium Gateway API Part 3: Boundaries in a Multi-Control-Plane ClusterSeparate the load balancers, node roles, and failure domains of a highly available Kubernetes control plane and the Cilium Gateway API data plane.Cilium Gateway API Part 4: Per-Node Cloud Public IPs Without an LBReceive external traffic with Cilium hostNetwork and DNS when cloud SDN associates a distinct public IP with each node VM.

Operations and Reliability

Distributed Failure Handling Part 3: How OpenStack and Kubernetes Converge After FailureCompare how OpenStack Nova and Kubernetes use durable state, asynchronous commands, idempotent reconciliation, and fencing instead of a global transaction.

Explore

  • Blog
  • Docs

Collections

  • Series

Feed

  • RSS

Language

  • 한국어

Elsewhere

  • jamie.kr ↗

Engineering Notes · Jamie