Restarting cilium daemonset on upgrade workflow to address upgrade issue #2066
+109
−1
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.
Issue #, if available:
#1888
Description of changes:
This PR restarts the cilium pods in a CloudStack upgrade workflow in order to prevent the issues observed in #1888. We are still waiting to hear what the root cause may be from Isovalent but expect this change to resolve the majority of the issues.
Created #2061 to make the logic non Cloudstack-specific
This PR was merged in main but the changes should be included in the upcoming release
Testing (if applicable):
Unit tests. Executed the TestCloudStackKubernetes120RedhatTo121Upgrade locally several times and observed the networking issues recover during the upgrade
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.