chore(Matomo): update mariadb crds to support v0.22.0 #434
Conversation
This file contains 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
pmig
approved these changes
Nov 27, 2023
1 task
Signed-off-by: Philip Miglinci <[email protected]>
pmig
force-pushed
the
mariadboperator-v0.22.0
branch
from
1bcce92
to
9ad7e88
Compare
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.
Upgrade notes
This is needed because k8s does not remove the
spec.imageproperty (that received an incompatible change in this update) but sets it to{}(which is no longer valid with the new crd version). If this step is skipped, neither the glasskube operator, nor the mariadb operator will be able to deserialize the objects and they have to be force deleted.