avirajkhare00 opened a new issue, #3098: URL: https://github.com/apache/iggy/issues/3098
## Context [#2932](https://github.com/apache/iggy/issues/2932) addressed **Helm chart** ingress being controller-agnostic (docs + `className` / annotations). The **Iggy Helm chart** itself is no longer nginx-specific. The **community** `kubernetes/ingress-nginx` controller is **[retired as of March 2026](https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/)** (no security fixes after that date). Our **CI / local smoke** path is still coupled to it: - `scripts/ci/setup-helm-smoke-cluster.sh` applies the upstream **kind** ingress-nginx manifest and waits for its admission webhook. - `scripts/ci/test-helm.sh` smoke defaults `HELM_SMOKE_INGRESS_CLASS` to `nginx` and expects that controller behavior for `curl` checks via localhost:80. ## Goal Decouple Helm **smoke / validation infrastructure** from ingress-nginx by switching to a **maintained** ingress implementation (or **Gateway API** + a supported implementation), and align `HELM_SMOKE_INGRESS_CLASS` / docs with the new default. ## Non-goals (can be separate issues) - Optional first-class **Gateway API** (`HTTPRoute`) support in the chart (larger feature than smoke CI). - Changing F5 / commercial NGINX products (different from community ingress-nginx). ## Suggested approach 1. Pick a default for **kind** smoke (e.g. **Traefik**, **Contour**, or **Cilium** — whichever is simplest to install in kind and stable in CI). 2. Update `setup-helm-smoke-cluster.sh`, `test-helm.sh`, and **Helm README** smoke sections to match (`ingressClassName` / host routing). 3. Keep a short note in docs that **ingress-nginx** is retired for anyone still copying old snippets. ## Related - Closes the loop after [#2932](https://github.com/apache/iggy/issues/2932) for **repository automation**, not chart templates. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
