Re: [I] helm: setup an ingress other than nginx [iggy]

["avirajkhare00 (via GitHub)" <gi...@apache.org>]

avirajkhare00 commented on issue #2932:
URL: https://github.com/apache/iggy/issues/2932#issuecomment-4064467837

   I would like to take this.
   
   I checked the chart before replying. The current Helm templates are already mostly ingress-controller-agnostic: `helm/charts/iggy/templates/ingress.yaml` supports `className` and annotations, and `helm/charts/iggy/values.yaml` does not hard-code nginx behavior. The nginx-specific coupling looks mostly documentation and examples level right now, especially in `helm/charts/iggy/README.md`.
   
   My plan is:
   1. Confirm whether the gap is documentation and examples only, or whether we also need chart values or templates for a controller-neutral path.
   2. Remove nginx-specific assumptions from the chart docs and example values where possible.
   3. If needed, add a cleaner controller-agnostic configuration story rather than baking in a new controller-specific path.
   
   I would keep the change minimal and controller-neutral unless the maintainers specifically want Gateway API support in the chart itself.


-- 
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: commits-unsubscribe@iggy.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org