ops-demo/manifests/networking/ingress-nginx/values.yaml
Paul Harkink 633f3f6e46 feat(ex03): MetalLB + Ingress-Nginx + podinfo ingress
- apps/networking/metallb.yaml: MetalLB Helm app (chart 0.14.9)
- apps/networking/metallb-config.yaml: IPAddressPool + L2Advertisement CRDs
- apps/networking/ingress-nginx.yaml: Ingress-Nginx Helm app (chart 4.12.0)
- manifests/networking/metallb/: values.yaml + metallb-config.yaml (pool 192.168.56.200-220)
- manifests/networking/ingress-nginx/values.yaml: LB IP 192.168.56.200, class nginx
- manifests/apps/podinfo/ingress.yaml: podinfo.192.168.56.200.nip.io
- docs/03-metallb-ingress.md: Exercise 03 participant guide
- manifests/argocd/values.yaml: ArgoCD ingress block commented (enabled in Ex03)
2026-02-28 15:28:39 +01:00

17 lines
425 B
YAML

# Ingress-Nginx Helm values
# The controller's LoadBalancer service will get 192.168.56.200 from MetalLB.
# All workshop ingresses use IngressClass "nginx".
controller:
ingressClassResource:
name: nginx
default: true
service:
type: LoadBalancer
# Request a specific IP so docs can reference it reliably
loadBalancerIP: "192.168.56.200"
resources:
requests:
cpu: 100m
memory: 128Mi