(feat) Introduce init container #1606
Merged
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
Hash functions have changed since release v1.4.0. When Sveltos detects a hash change, it triggers a redeployment of the resources listed in the profile (Helm charts or raw Kubernetes resources). This PR introduces an initialization phase to handle this transition gracefully. By pre-calculating and updating these hashes before the main controller starts, we ensure the controller does not misinterpret the new hashing logic as a configuration change. This prevents unnecessary, redeployments across all managed clusters that would otherwise occur when the controller detects a mismatch between the stored and newly calculated hashes.
gianlucam76
force-pushed
the
init-container
branch
from
f4a18e2 to
810545c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hash functions have changed since release v1.4.0.
When Sveltos detects a hash change, it triggers a redeployment of the resources listed in the profile (Helm charts or raw Kubernetes resources).
This PR introduces an initialization phase to handle this transition gracefully. By pre-calculating and updating these hashes before the main controller starts, we ensure the controller does not misinterpret the new hashing logic as a configuration change. This prevents unnecessary, redeployments across all managed clusters that would otherwise occur when the controller detects a mismatch between the stored and newly calculated hashes.