Skip to content

Kubernetes

Kubernetes architecture diagrams covering ingress controllers, service mesh patterns, pod networking, and container security with NGINX and F5 XC integration.

Container-based application with NGINX ingress controller distributing traffic to frontend and backend pods.

architecture-beta
  group cluster(hashicorp-flight:kubernetes-color)[Kubernetes Cluster]
  group frontend(carbon:container-services)[Frontend Pods] in cluster
  group backend(carbon:container-services)[Backend Pods] in cluster

  service ingress(carbon:gateway)[Ingress Controller] in cluster
  service web(hashicorp-flight:docker-color)[Web App] in frontend
  service api(carbon:api)[API Service] in backend
  service db(carbon:data-base)[StatefulSet DB] in backend

  ingress:R --> L:web
  ingress:B --> T:api
  api:R --> L:db

Kubernetes service mesh with F5 XC providing external load balancing, observability, and multi-cluster connectivity.

architecture-beta
  group xc(lucide:cloud)[F5 XC]
  group mesh(hashicorp-flight:kubernetes-color)[Service Mesh]

  service nginx(f5xc:nginx-one)[NGINX One] in xc
  service obs(f5xc:observability)[Observability] in xc
  service proxy1(carbon:server-proxy)[Sidecar Proxy] in mesh
  service svc1(hashicorp-flight:docker-color)[Service A] in mesh
  service proxy2(carbon:server-proxy)[Sidecar Proxy] in mesh
  service svc2(hashicorp-flight:docker-color)[Service B] in mesh

  nginx:R --> L:obs
  obs:R --> L:proxy1
  proxy1:R --> L:svc1
  svc1:B --> T:proxy2
  proxy2:R --> L:svc2

CI/CD pipeline for Kubernetes deployments using Helm charts, container registry, and automated rollouts.

flowchart LR
  dev@{ icon: 'lucide:user', label: 'Developer' }
  repo@{ icon: 'carbon:application', label: 'Git Repo' }
  ci@{ icon: 'carbon:cloud-services', label: 'CI Pipeline' }
  registry@{ icon: 'hashicorp-flight:docker-color', label: 'Container Registry' }
  helm@{ icon: 'hashicorp-flight:helm-color', label: 'Helm Deploy' }
  k8s@{ icon: 'hashicorp-flight:kubernetes-color', label: 'K8s Cluster' }

  dev --> repo
  repo --> ci
  ci --> registry
  registry --> helm
  helm --> k8s