fix: reject ddc compute group storage template changes#496
Merged
morningman merged 1 commit intoJun 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Changing BE file cache paths or persistent volume settings after a DDC compute group has been created changes the generated StatefulSet volume claim templates. Kubernetes does not allow updating StatefulSet volumeClaimTemplates in place, so the reconcile currently fails later with a low-level immutable field error. This makes the failure hard to understand and can look like a generic StatefulSet apply problem.
This change detects the storage template change before applying the StatefulSet and returns a clear operator event telling users to recreate the compute group for this kind of storage layout change.
Summary
Tests
Notes