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
When using Tenant CR and exposing services via LoadBalancer type, a MetalLB annotation is added to a service by Openshift noting that an address was allocated. This however conflicts with operator Service object check and the operator tries to reconcile/remove the annotations, after which metallb adds it back.
The Services object is being endlessly updated, which generates unnecessary load for Kubernetes API server.
This results in Service object being constantly updated back and forth, in operator logs we see:
I0620 10:14:42.250078 1 minio-services.go:64] MinIO Services don't match: service annotations don't match
I0620 10:14:42.642629 1 console.go:74] Console Service don't match: service annotations don't match. Conciliating
One can argue that metallb should not possibly add annotations to an owned object, however, the logic in service reconciliation could be updated so that extra annotations and possibly labels are ignored during reconciliation.
Another workaround would the to place annotation in the CR, but this seems awkward:
When using Tenant CR and exposing services via LoadBalancer type, a MetalLB annotation is added to a service by Openshift noting that an address was allocated. This however conflicts with operator Service object check and the operator tries to reconcile/remove the annotations, after which metallb adds it back.
The Services object is being endlessly updated, which generates unnecessary load for Kubernetes API server.
This is relevant portion of tenant CR:
The generated Service annotations:
This results in Service object being constantly updated back and forth, in operator logs we see:
I0620 10:14:42.250078 1 minio-services.go:64] MinIO Services don't match: service annotations don't match
I0620 10:14:42.642629 1 console.go:74] Console Service don't match: service annotations don't match. Conciliating
One can argue that metallb should not possibly add annotations to an owned object, however, the logic in service reconciliation could be updated so that extra annotations and possibly labels are ignored during reconciliation.
Another workaround would the to place annotation in the CR, but this seems awkward:
The text was updated successfully, but these errors were encountered: