Fix: The hash generation is broken, because an omitempty was removed
#52
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
This means rthat in production ALL pods are restarting, which is unwanted. For now a breaking API change has been applied to explicit set the value. We already has a ticket to harmonize the complete CRD API.
Robert-Stam
changed the title
omitempty was removedomitempty was removed
Robert-Stam
changed the title
omitempty was removedomitempty was removed
bashofmann
approved these changes
Dec 9, 2024
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.
This means that in production ALL pods are restarting, which is unwanted. For now a breaking API change has been applied to explicit set the value. We already has a ticket to harmonize the complete CRD API.