(fix): Preserve immutable fields during upgrade #131
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
rhdedgar
approved these changes
Aug 1, 2025
mfleader
requested changes
Aug 1, 2025
VaishnaviHire
force-pushed
the
fix_upgrade_error
branch
from
8237051 to
b5eaaef
Compare
During upgrades, if we do server-side apply without preserving the selectors field, we get 'field is immutable' error which blocks deployment updates and also causes continuous operator reconciliation. Preserving exists selector values fixes the issue. Signed-off-by: Vaishnavi Hire <vhire@redhat.com>
VaishnaviHire
force-pushed
the
fix_upgrade_error
branch
from
b5eaaef to
b75cbec
Compare
mfleader
approved these changes
Aug 1, 2025
VaishnaviHire
added a commit
to VaishnaviHire/llama-stack-k8s-operator
that referenced
this pull request
Aug 19, 2025
During upgrades, if we do server-side apply without preserving the selectors field, we get 'field is immutable' error which blocks deployment updates and also causes continuous operator reconciliation. Preserving existing selector values fixes the issue. Approved-by: rhdedgar Approved-by: mfleader (cherry picked from commit e2cc886)
VaishnaviHire
added a commit
to VaishnaviHire/llama-stack-k8s-operator
that referenced
this pull request
Sep 18, 2025
During upgrades, if we do server-side apply without preserving the selectors field, we get 'field is immutable' error which blocks deployment updates and also causes continuous operator reconciliation. Preserving existing selector values fixes the issue. Approved-by: rhdedgar Approved-by: mfleader (cherry picked from commit e2cc886)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
During upgrades, if we do server-side apply without preserving the selectors field, we get 'field is immutable' error which blocks deployment updates and also causes continuous operator reconciliation. Preserving existing selector values fixes the issue.