avirajkhare00 opened a new pull request, #2976: URL: https://github.com/apache/iggy/pull/2976
## Which issue does this PR close? Closes # https://github.com/apache/iggy/issues/2975 This PR is mainly for #2975, but it also partially cleans up #2932 by making the README ingress example controller-neutral. ## Rationale Local `kind` testing showed two real Helm chart bugs: the server deployment was not getting the documented default `podSecurityContext`, and the UI health probes were hitting a route that returns `404`. ## What changed? On a clean Helm install, the server deployment rendered the wrong pod security context because the template looked for `server.podSecurityContext` even though the chart defines `podSecurityContext` at the root. The UI deployment also used `/` for liveness and readiness probes, but the web UI returns `404` on that path, so Kubernetes kept restarting the pod. The fix makes the server deployment use the root `podSecurityContext` value and changes the UI probe path to `/auth/sign-in`, which returns `200`. I also updated the chart README to clarify the `ServiceMonitor` prerequisite, note the local `io_uring` caveat seen during testing, and use more controller-neutral ingress wording. ## Local Execution - Partially passed. - `helm lint ./helm/charts/iggy` passed. - `helm install iggy ./helm/charts/iggy -n iggy-test --create-namespace --set server.serviceMonitor.enabled=false` was run on a local `kind` cluster. - After the template changes, the server deployment rendered the expected root `podSecurityContext`, and the UI became healthy with `/auth/sign-in` as the probe path. - Full local startup still did not fully pass because the server hit a separate `io_uring` / runtime `Invalid argument` failure on `kind`. That looks like a different issue and is not fixed in this change. - Pre-commit hooks not ran. `prek` was not installed/configured in this checkout, and only the sample git hooks were present. ## AI Usage 1. Tool used: OpenAI Codex / ChatGPT. 2. Scope: investigation, small Helm template changes, README updates, and drafting the issue/PR text. 3. Verification: I ran `helm lint`, installed the chart on local `kind`, inspected rendered pod specs, checked pod logs and Kubernetes events, and verified the UI route behavior with local HTTP checks. 4. Yes, I can explain every line of the change if asked. -- 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]
