avirajkhare00 opened a new pull request, #3386:
URL: https://github.com/apache/iggy/pull/3386
## Which issue does this PR address?
Closes #3098
## Rationale
Ingress NGINX was officially retired in March 2026. Our Helm smoke/CI
cluster setup still pulled the retired controller, which gets no further
security or bug fixes.
## What changed?
**`scripts/ci/setup-helm-smoke-cluster.sh`**
- Removed nginx-specific kind config (ingress-ready label, hostPort
mappings, admission-webhook polling helpers).
- Install Envoy Gateway via Helm first, then upgrade Gateway API CRDs to
v1.5.0 with `--server-side --force-conflicts`. This ordering avoids the
safe-upgrade ValidatingAdmissionPolicy blocking EG's older bundled CRDs.
- Creates an EnvoyProxy (NodePort), GatewayClass, and Gateway resource,
then waits for the Programmed condition.
**`scripts/ci/test-helm.sh`**
- Removed `HELM_SMOKE_INGRESS_CLASS`; chart is now deployed without Ingress
objects.
- After helm install, applies two HTTPRoute resources pointing at the chart
Services (server :3000, UI :3050).
- Uses `kubectl port-forward` to expose the gateway on `127.0.0.1:8080`,
which works on both Linux CI runners and macOS (unlike direct NodePort
access, which fails inside Docker Desktop's VM).
## Local Execution
- Passed
- Pre-commit hooks ran
## AI Usage
If AI tools were used, please answer:
1. Which tools? (e.g., GitHub Copilot, Claude, ChatGPT) -> Claude
2. Scope of usage? - fixed existing code
3. How did you verify the generated code works correctly? -> ran and
verified all locally
4. Can you explain every line of the code if asked? -> YES
--
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]
