# ConfigMap with NGINX config for request splitting
apiVersion: v1
kind: ConfigMap
metadata:
name: experiment-config
data:
nginx.conf: |
worker_processes 5;
events { worker_connections 1024; }
http {
upstream backend {
ip_hash;
server legacy-service:8080 weight=9;
server new-service:8080;
}
server {
listen 80;
location / {
proxy_pass http://backend;
proxy_set_header Host $host;
}
}
}
---
# Ambassador Pod running NGINX
apiVersion: v1
kind: Pod
metadata:
name: ambassador-experiment
spec:
containers:
- name: nginx
image: nginx:latest
resources:
requests:
memory: "64Mi"
cpu: "100m"
limits:
memory: "128Mi"
cpu: "200m"
volumeMounts:
- name: config-volume
mountPath: /etc/nginx/
ports:
- containerPort: 80
volumes:
- name: config-volume
configMap:
name: experiment-config
Rewriting a critical service? Use the Ambassador Pattern: route real traffic to both old & new versions via NGINX, validating features & measuring performance—risk-free. Modernize with confidence! #SystemDesign #DevOps #FeatureParity #PerformanceTesting