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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Is your feature request related to a problem? Please describe.
We are currently trying to rollout Consul to our Kubernetes cluster. We have a non-default nginx ingress controller setup that uses a custom ingress class. Unfortunately it appears there is no way to set the ingressClassName for the UI ingress object using the Chart currently, which means we are unable to access the Consul UI on our cluster.
Feature Description
By adding the ability to specify an ingressClassName for the UI ingress we can expose the Consul UI from our Kubernetes cluster.
Use Case(s)
This is useful if you have a non-default Kubernetes cluster with some additional requirements.
Contributions
This would probably not be a big change so I wouldn't mind sending in a PR if it has a chance of being accepted.
The text was updated successfully, but these errors were encountered:
Community Note
Is your feature request related to a problem? Please describe.
We are currently trying to rollout Consul to our Kubernetes cluster. We have a non-default nginx ingress controller setup that uses a custom ingress class. Unfortunately it appears there is no way to set the ingressClassName for the UI ingress object using the Chart currently, which means we are unable to access the Consul UI on our cluster.
Feature Description
By adding the ability to specify an ingressClassName for the UI ingress we can expose the Consul UI from our Kubernetes cluster.
Use Case(s)
This is useful if you have a non-default Kubernetes cluster with some additional requirements.
Contributions
This would probably not be a big change so I wouldn't mind sending in a PR if it has a chance of being accepted.
The text was updated successfully, but these errors were encountered: