Add nodeAffinity for Postgres operator, and add new entry cloud-native-postgresql-v1.22 #2313
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.
What this PR does / why we need it:
Affinity
field for Postgres operator CSV/deployment. So the configuration for Postgres Operator should contain necessarynodeAffinity
to ensure pods are distributed on nodes with supported architecture.cloud-native-postgresql-v1.22
in OperatorConfig, so the Postgres operator requested viacloud-native-postgresql-v1.22
will get the multi replicas configuration as well.Which issue(s) this PR fixes:
Fixes https://github.ibm.com/IBMPrivateCloud/roadmap/issues/65071
Test
docker-na-public.artifactory.swg-devops.com/hyc-cloud-private-scratch-docker-local/ibmcom/common-service-operator-amd64:dev
andImagePullPolicy: Always
cloud-native-postgresql-v1.22
affinity
section matching with what we defined in OperatorConfig