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
While working on #5651 I noticed that we update the services created by the operator on every single reconciliation.
This seems to be caused by a diff in ClusterIPs where we ignore ClusterIPs when they are not a parseable IP as it is the case for None.
I don't recall why we have this special casing of non-IPs, I suspect a validation in an older version of Kubernetes might have been at play as I don't think it is there without reason. In any case we should revisit this and see if we can avoid unnecessary updates.
This needs to be tested across k8s versions probably to avoid any breakage.
The text was updated successfully, but these errors were encountered:
While working on #5651 I noticed that we update the services created by the operator on every single reconciliation.
This seems to be caused by a diff in
ClusterIPs
where we ignoreClusterIPs
when they are not a parseable IP as it is the case forNone
.I don't recall why we have this special casing of non-IPs, I suspect a validation in an older version of Kubernetes might have been at play as I don't think it is there without reason. In any case we should revisit this and see if we can avoid unnecessary updates.
This needs to be tested across k8s versions probably to avoid any breakage.
The text was updated successfully, but these errors were encountered: