Updated pgo-osb for PGO v3.4.0 #13
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
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.
pgo-osb has been updated to function properly with version 3.4.0 of the postgres-operator. This includes updating the CO_APISERVER_VERSION that is set when creating the pgo-osb deployment, as well as updating the dep dependency defined for the postgres-operator.
Specifically addresses the issues described in the followed ticket when running the current version of pgo-osb (v1.1.0) against v3.4.0 of the postgres-operator: #12
Also added dep overrides for the k8s.io/apimachinery, k8s.io/client-go and k8s.io/api dependencies to avoid potential conflicts.
Additionally, updated pgo-osb version to 1.2.0 in the dockerfile and README.
Closes #12