fix: automatically roll tigera-operator deployment when managed kubernetes-services-endpoint ConfigMap is changed #11343
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…netes-services-endpoint cm is changed
marvin-tigera
added
release-note-required
|
|
Algeran
changed the title
caseydavenport
approved these changes
Nov 7, 2025
Member
|
/sem-approve |
Member
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When kubernetes-services-endpoint ConfigMap is managed by helm release (
kubernetesServiceEndpoint.hostproperty is specified), any change to the host/port property will not trigger the rollout of tigera-operator deployment. In this case, environment variables in the process of the operator are not updated and it requires manual restart of the deployment.This change adds the checksum annotation to pod annotations and in case if the ConfigMap is managed by helm release and if it's changed, the checksum will be changed as well and it will trigger an automatic rollout.
Related issues/PRs
Based on answer in QA: https://github.com/orgs/projectcalico/discussions/11332
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.