Repository navigation
Commit 3958dd1
committed
docs(gateway): state the passthrough limitations and upgrade effects
Three things an operator could previously only discover by hitting
them: one listener per port, so two instances of one engine cannot
share its native port by SNI; the field is chart-rendered, so a
kubectl edit adding listeners is drift Flux reverts; and the schema
tightening on apex and tlsPassthroughServices applies on the next write
of objects that already exist, so a hand-edited upper-case apex fails
its release on upgrade rather than at install.
Both restrictions trace to the pinned Cilium selecting a passthrough
backend by SNI alone, so both are noted as revisitable when the pin
moves.
Assisted-By: Claude <[email protected]>
Signed-off-by: Aleksei Sviridkin <[email protected]>1 parent e806319 commit 3958dd1
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
75 | 75 | | |
76 | 76 | | |
77 | 77 | | |
78 | | - | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
79 | 83 | | |
80 | 84 | | |
81 | 85 | | |
| |||
0 commit comments