Will calico re-sync envs from kubernetes-services-endpoint on tigera-operator helm release upgrade?

[Algeran]

We have calico installed using the tigera-operator helm chart and kubernetes-services-endpoint ConfigMap is a part of the helm release. If I change helm values for host or port, it will definitely update the config map, but it looks like tigera-operator deployment pods will not be restarted. Do it have any internal mechanism to re-sync envs from this ConfigMap? If it's not, I'll rise an issue to add the configmap checksum annotation to tigera-operator Deployment

[caseydavenport]

I don't think there's an automated way right now - just need to restart the operator pod after adjusting the env vars.