Conversation
This commit removes redis deployment and its resources from eda-server-operator without introducing breaking changes. By keeping the fields in the CRD schema and ignoring them in the eda role, we maintain backwards compatibility and guarantee that upgrades will not cause the operator to break. A scenario where the operator is installed in multiple namespaces and the CRD is shared is also covered and won't fail this way. The fields will be removed from the CRD schema in a future `apiVersion` bump, as specified in the documentation.
|
kaiokmo
changed the title
andresberejnoi
approved these changes
Mar 9, 2026
dsavineau
approved these changes
Mar 9, 2026
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
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.
This commit removes redis deployment and its resources from eda-server-operator without introducing breaking changes. By keeping the fields in the CRD schema and ignoring them in the eda role, we maintain backwards compatibility and guarantee that upgrades will not cause the operator to break.
A scenario where the operator is installed in multiple namespaces and the CRD is shared is also covered and won't fail this way.
The fields will be removed from the CRD schema in a future
apiVersionbump, as specified in the documentation.