fix: specify olm version #436
Merged
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
This commit updates the `cluster.sh` to explicitly use a fixed OLM version, resolving issue where the `operator-sdk` defaults to the latest OLM version. The latest OLM version `v0.29.0` has an issue affecting pod deployments on KinD clusters causing failures Signed-off-by: vprashar2929 <[email protected]>
sthaha
approved these changes
Oct 28, 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 commit updates the
cluster.shto explicitly use a fixed OLM version, resolving issue where theoperator-sdkdefaults to the latest OLM version. The latest OLM versionv0.29.0has an issue affecting pod deployments on KinD clusters causing failuresRef: operator-framework/operator-lifecycle-manager#3419