Update deploy-k8s-service doc with ProxyGroup ingress pattern #166

Merged

eblume merged 1 commit from docs/update-deploy-k8s-ingress into main

2026-02-11 21:10:43 -08:00

eblume commented

2026-02-11 21:09:57 -08:00

Owner

Summary

Updated the "Configure Ingress" section to use the current ProxyGroup pattern (proxy-group: "ingress", defaultBackend, tls.hosts)
Replaced the old per-ingress proxy example that used rules: with host: (which breaks ProxyGroup routing)
Added key points explaining why defaultBackend is required and what each annotation does
Updated checklist to mention ProxyGroup

Test plan

Review rendered doc for accuracy against existing ingress manifests

## Summary - Updated the "Configure Ingress" section to use the current ProxyGroup pattern (`proxy-group: "ingress"`, `defaultBackend`, `tls.hosts`) - Replaced the old per-ingress proxy example that used `rules:` with `host:` (which breaks ProxyGroup routing) - Added key points explaining why `defaultBackend` is required and what each annotation does - Updated checklist to mention ProxyGroup ## Test plan - [ ] Review rendered doc for accuracy against existing ingress manifests

eblume added 1 commit

2026-02-11 21:09:57 -08:00

Update deploy-k8s-service doc with ProxyGroup ingress pattern ca0040f787

The ingress example was using the old per-ingress proxy pattern with
rules/host, which doesn't work with ProxyGroup routing. Updated to
match the current pattern: proxy-group annotation, defaultBackend
instead of rules, and tls.hosts for MagicDNS hostname.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>