Container OrchestrationArchitect: Ajit Dev (@ajitdev01)Katihar, Bihar, India
Kubernetes Operations & EKS Cluster Topologies
Architecting production Kubernetes clusters on AWS EKS. Zero-downtime rolling updates, Horizontal Pod Autoscaling (HPA), NetworkPolicy security isolation, and Ingress routing.
Zero-Downtime Rolling Updates
Horizontal Pod Autoscaling (HPA)
NetworkPolicy Security Segmentation
EKS Managed Node Groups
1. Production Kubernetes Deployment with Health Probes
Guaranteed Zero-Downtime Rolling Release Strategy
Tested Deployment manifest engineered by Ajit Dev with explicit CPU/Memory limits, liveness/readiness probes, and zero-downtime rolling update parameters:
# k8s/deployment.yml — Hardened Microservice Spec
apiVersion: apps/v1
kind: Deployment
metadata:
name: ajitdev-web-app
namespace: production
labels:
app: ajitdev-web
spec:
replicas: 3
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 1
maxUnavailable: 0
selector:
matchLabels:
app: ajitdev-web
template:
metadata:
labels:
app: ajitdev-web
spec:
containers:
- name: web
image: ajitdev/web-app:latest
ports:
- containerPort: 3000
resources:
requests:
cpu: "100m"
memory: "256Mi"
limits:
cpu: "500m"
memory: "512Mi"
readinessProbe:
httpGet:
path: /api/health
port: 3000
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /api/health
port: 3000
initialDelaySeconds: 15
periodSeconds: 20
2. NetworkPolicy Pod Isolation (Zero Lateral Movement)
Restricting Ingress Exclusively to Ingress Controllers
Restricting pod communication so that compromised containers cannot access backend databases directly without going through approved application microservices:
# k8s/network-policy.yml — Restrict Ingress
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: isolate-database-ingress
namespace: production
spec:
podSelector:
matchLabels:
role: database
policyTypes:
- Ingress
ingress:
- from:
- podSelector:
matchLabels:
app: ajitdev-web
ports:
- protocol: TCP
port: 5432