Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger destination restart upon every upgrade #6954

Merged
merged 1 commit into from
Sep 23, 2021
Merged

Conversation

alpeb
Copy link
Member

@alpeb alpeb commented Sep 22, 2021

Fixes #6940

Upon every upgrade the certs used by the policy controller validator
change, but the controller doesn't detect that, which breaks the webhook
requests. As a temporary solution, we force the pod to restart by adding
a checksum/config annotation to the manifest, like the injector
currently has.

Fixes #6940

Upon every upgrade the certs used by the policy controller validator
change, but the controller doesn't detect that, which breaks the webhook
requests. As a temporary solution, we force the pod to restart by adding
a `checksum/config` annotation to the manifest, like the injector
currently has.
@alpeb alpeb requested a review from a team as a code owner September 22, 2021 20:31
Copy link
Contributor

@Pothulapati Pothulapati left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alpeb alpeb merged commit 889fc2e into main Sep 23, 2021
@alpeb alpeb deleted the alpeb/destination-restart branch September 23, 2021 11:17
alpeb added a commit that referenced this pull request Sep 23, 2021
Followup to #6932 that modified `destination-rbac.yaml`. #6954 used that
file to calculate the new `checksum/config` annotation, so long story
short, both PRs weren't aware of each other.
@alpeb alpeb mentioned this pull request Sep 23, 2021
alpeb added a commit that referenced this pull request Sep 23, 2021
Followup to #6932 that modified `destination-rbac.yaml`. #6954 used that
file to calculate the new `checksum/config` annotation, so long story
short, both PRs weren't aware of each other.
alpeb added a commit that referenced this pull request Sep 23, 2021
Policy CRD changes (#6943) merged and changed `destination-rbac.yml`, and didn't have as an ancestor the changes from #6954 that calculate that file's sha. This PR then updates that SHA in the golden files.
@alpeb alpeb mentioned this pull request Sep 23, 2021
alpeb added a commit that referenced this pull request Sep 23, 2021
Policy CRD changes (#6943) merged and changed `destination-rbac.yml`, and didn't have as an ancestor the changes from #6954 that calculate that file's sha. This PR then updates that SHA in the golden files.
@iAnomaly
Copy link
Contributor

Hey @alpeb, I am hitting issue #6940 as recently as version 30.13.0-edge and noticed the fix you implemented in this PR was dropped in #6635 Was this intentional or maybe a bad copy/paste/merge?

@alpeb
Copy link
Member Author

alpeb commented Sep 28, 2023

Thanks for the report @iAnomaly . That was indeed an oversight. I'll ping the team about it, but feel free to post a PR addressing that (and for other controllers as well if needed) 😉

@iAnomaly
Copy link
Contributor

Done @alpeb: #11440

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrading sometimes requires restarting linkerd-destination
4 participants