Bump operator newest v2.3.0-24.3.1 version #1600
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
RafalKorepta
requested review from
JakeSCahill,
andrewstucki and
chrisseto
as code owners
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
from
0a68241 to
82e70d3
Compare
Contributor
|
I think we're waiting on #1595 to bump the operator release? |
Contributor
|
Oh and we need to wait for the docker tag to get fixed as well, right? |
Contributor
Author
|
You are right! |
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
4 times, most recently
from
d459354 to
22bac28
Compare
RafalKorepta
changed the title
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
from
22bac28 to
fca8141
Compare
RafalKorepta
changed the title
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
3 times, most recently
from
e1fa32a to
3fe7433
Compare
RafalKorepta
changed the title
RafalKorepta
changed the title
Prior to this commit the operator chart's declared permissions had grown out of sync with those declared by the operator itself. This commit re-synchronizes the permissions, adds in regression tests to prevent such drift from happening again, and releases the updated chart. Co-authored-by: Rafal Korepta <rafal.korepta@gmail.com>
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
from
3fe7433 to
7c735c4
Compare
RafalKorepta
force-pushed
the
rk/release-operator-v2.3.0
branch
from
7c735c4 to
ead31b1
Compare
birdayz
approved these changes
Nov 22, 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.
Based on #1595
This PR adds to the Github filters
value.yamlfile as it should be validated when anything has changed. There can be argument that any change to thevalues.yamlshould changechart.yamltoo, but in this is not the case 100% of times.The operator
chart.yamldefinition now will point to the latest operator releasev2.3.0-24.3.1.P.S. The release was removed as there was panic found in the configurator. It's already fixed with redpanda-data/redpanda-operator#311. Now the release is blocked by connectors go based translation. Which will be solved in the next helm-chart PR.