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
Using OCP4.10.47. We've created a service and defined an IP address in spec.ExternalIPs.
Keepalived operator sucessfully brings up the ExternalIP as a VIP, but doesn't write back the service status updating the service.status.loadBalancer.ingress[0].ip.
If dynamic ExternalIP is used, the service.status.loadBalancer.ingress[0].ip does get updated (from what I can tell, not by the keepalived operator).
Is this a missing feature of keepalived operator or is the update of the service.spec when using a static ExternalIP supposed to be done by a different process within openshift? According to redhat support, the updating of the service.status should be done by the external loadbalancer.
The text was updated successfully, but these errors were encountered:
Using OCP4.10.47. We've created a service and defined an IP address in spec.ExternalIPs.
Keepalived operator sucessfully brings up the ExternalIP as a VIP, but doesn't write back the service status updating the service.status.loadBalancer.ingress[0].ip.
If dynamic ExternalIP is used, the service.status.loadBalancer.ingress[0].ip does get updated (from what I can tell, not by the keepalived operator).
Is this a missing feature of keepalived operator or is the update of the service.spec when using a static ExternalIP supposed to be done by a different process within openshift? According to redhat support, the updating of the service.status should be done by the external loadbalancer.
The text was updated successfully, but these errors were encountered: