Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Add affinity customization #492

Merged
merged 1 commit into from
Feb 1, 2021
Merged

Conversation

kppullin
Copy link
Contributor

What changes were proposed in this pull request?

For charts that have existing affinity hard-coded configs
defined, add support for overriding the hard-coded values.

For charts that lack affinity config entirely, add
support for injecting custom affinity values.

How was this patch tested?

Tested locally using helm template:
helm template <CHART>
helm template <CHART> --set affinity=test
diff <(helm template <CHART>) <(helm template <CHART> --set affinity=test)

For charts that have existing `affinity` hard-coded configs
defined, add support for overriding the hard-coded values.

For charts that lack `affinity` config entirely, add
the support for injecting custom affinity values.
@ghost
Copy link

ghost commented Jan 28, 2021

@confluentinc It looks like @kppullin just signed our Contributor License Agreement. 👍

Always at your service,

clabot

@@ -61,6 +61,10 @@ nodeSelector: {}
## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []

## Pod scheduling constraints
## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that the cp-control-center's deployment template already includes logic to conditionally use the Values.affinity config, however the affinity block is missing from this values.yaml file.

@gAmUssA
Copy link
Contributor

gAmUssA commented Feb 1, 2021

Thank you @kppullin

@gAmUssA gAmUssA merged commit c687428 into confluentinc:master Feb 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants