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
EG needs to set the Gateway.Status.Addresses field with the address that is bound for the Gateway (i.e. the Envoy LB service address). This is necessary in order to make progress with Gateway API conformance.
A related question: do all Gateways use the same address? Does this have the potential to cause any kind of conflict across Gateways/Routes?
A related question: do all Gateways use the same address? Does this have the potential to cause any kind of conflict across Gateways/Routes?
For the time being, I suggest we start off simple and have all Gateways use the same Service. Therefore, all Gateways will have the same address. A conflict can occur if a user specifies a Gateway address but I suggest we state this limitation in the v0.2.0 release notes and enforce it through validation. Thoughts @arkodg@LukeShu@youngnick?
EG needs to set the Gateway.Status.Addresses field with the address that is bound for the Gateway (i.e. the Envoy LB service address). This is necessary in order to make progress with Gateway API conformance.
A related question: do all Gateways use the same address? Does this have the potential to cause any kind of conflict across Gateways/Routes?
xref #65
The text was updated successfully, but these errors were encountered: