Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow placement control via helm #513

Merged
merged 1 commit into from
Aug 9, 2023
Merged

Conversation

cbgbt
Copy link
Contributor

@cbgbt cbgbt commented Aug 9, 2023

Issue number:
Closes #500

Description of changes:
This allows users to control tolerations, nodeSelector, and podAffinity/AntiAffinity via the helm values.yaml file.

apiserver pods have also been changed to have a podAntiAffinity for eachother by default.

Testing done:

  • Scheduled the agent onto a node with a taint by adding a toleration
  • Noted apiserver nodes weren't colocated unless forced by a taint
  • Constrained the controller with nodeSelector to a tainted node, causing it to become unschedulable. Fixed it by labeling an untainted node and also with a toleration.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

This allows users to control tolerations, nodeSelector, and
podAffinity/AntiAffinity via the helm values.yaml file.

apiserver pods have also been changed to have a podAntiAffinity for
eachother by default.
@cbgbt cbgbt merged commit 708e5f8 into bottlerocket-os:develop Aug 9, 2023
2 checks passed
@cbgbt cbgbt deleted the placement branch August 10, 2023 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Templating for tolerations / nodeselector throughout the helm chart
3 participants