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
It would be useful to be able to override the Ingress.status.loadBalancer.ingress entries that HAProxy maintains with arbitrary entries supplied by the user.
What HAProxy Ingress should do or how it should behave differently
Currently HAProxy can populate the status field based on a Service's status.loadBalancer.ingress field using the --publish-service option, but there are several occasions when using this isn't desirable. It would be nice to have a --publish-status-address or equivalent (that name comes from the NGINX Ingress Controller) option which could be used to publish arbitrary IP addresses and/or names in Ingress resources' status fields.
In my case I'm using a Linode NodeBalancer within LKE. This publishes an IPv4 address and a hostname but the NodeBalancer also has an IPv6 address associated with it that I'd like to use, so I would like to publish the IPv4 and IPv6 addresses in my Ingress resources. Other uses I see for this are publishing a CDN endpoint in the Ingress, or an arbitrary hostname. These are all useful when using ExternalDNS.
The text was updated successfully, but these errors were encountered:
What are you trying to do
It would be useful to be able to override the
Ingress.status.loadBalancer.ingress
entries that HAProxy maintains with arbitrary entries supplied by the user.What HAProxy Ingress should do or how it should behave differently
Currently HAProxy can populate the status field based on a Service's
status.loadBalancer.ingress
field using the--publish-service
option, but there are several occasions when using this isn't desirable. It would be nice to have a--publish-status-address
or equivalent (that name comes from the NGINX Ingress Controller) option which could be used to publish arbitrary IP addresses and/or names in Ingress resources' status fields.In my case I'm using a Linode NodeBalancer within LKE. This publishes an IPv4 address and a hostname but the NodeBalancer also has an IPv6 address associated with it that I'd like to use, so I would like to publish the IPv4 and IPv6 addresses in my Ingress resources. Other uses I see for this are publishing a CDN endpoint in the Ingress, or an arbitrary hostname. These are all useful when using ExternalDNS.
The text was updated successfully, but these errors were encountered: