You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy/README.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,10 +145,11 @@ The two most important dynamic Services currently are:
145
145
146
146
Notes:
147
147
148
-
-`nantian-gw-dataplane` is the shared frontend entry; current Kind smoke defaults to using it.
148
+
-`nantian-gw-dataplane` is the shared frontend entry, mainly useful for shared-node exposure patterns such as Kind NodePort access.
149
149
-`nantian-gw-<gatewayName>` is a dedicated Service derived from the Gateway name; for example, if the `Gateway` is named `edge`, the corresponding Service is typically `nantian-gw-edge`.
150
150
- per-Gateway Services default to `ClusterIP`, but can be lowered to `NodePort` or `LoadBalancer` via `Gateway.spec.infrastructure.parametersRef`, making them the more natural north-south exposure point in long-term environments.
151
151
- These objects are maintained by the control plane reconcile loop and are not static install assets from `deploy/kubernetes/base/`.
152
+
- Because these derived frontend Services are backed by controller-managed EndpointSlices rather than a pod selector, `kubectl port-forward service/...` is not the right validation path for smoke tests; use real Service traffic from inside the cluster or a normal client entry point instead.
152
153
153
154
## Traffic Entry Relationships
154
155
@@ -179,7 +180,8 @@ The most easily confused aspect of the current repository is that the entries se
| Smoke validation |`nantian-gw-<gatewayName>`| Current smoke validates the derived per-Gateway Service from inside the cluster so selectorless frontend Services are exercised through normal Service routing |
183
185
| Long-term / production |`nantian-gw-<gatewayName>`| Better to expose per Gateway individually, then control `ClusterIP` / `NodePort` / `LoadBalancer` via `parametersRef`|
fail "GET /echo via $GATEWAY_SERVICE did not succeed within ${TIMEOUT}s${detail}"
250
304
return 1
251
305
}
252
306
253
307
# ── Main ──
254
308
main() {
255
-
trap'FAILED=true' ERR
256
-
trap'cleanup_cluster; if $FAILED; then red "✗ Smoke test FAILED"; else green "✓ Smoke test PASSED"; fi' EXIT
309
+
trap'exit_code=$?; if [[ "$exit_code" -ne 0 ]]; then FAILED=true; fi; cleanup_cluster; if $FAILED; then red "✗ Smoke test FAILED"; else green "✓ Smoke test PASSED"; fi; exit "$exit_code"' EXIT
0 commit comments