Skip to content

Unable to configure tolerations for kcp, etcd and front proxy #135

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

Open
martivo opened this issue Apr 24, 2025 · 3 comments
Open

Unable to configure tolerations for kcp, etcd and front proxy #135

martivo opened this issue Apr 24, 2025 · 3 comments

Comments

@martivo
Copy link

martivo commented Apr 24, 2025

It is not possible to create toleration configurations for front-proxy, kcp and etcd Pods. It is possible to configure affinity but this is usually combined with a toleration in case there are dedicated nodes for some pods.

Propose to add

etcd:
    tolerations: []
kcp:
    tolerations: []
kcpFrontProxy:
    tolerations: []

Usage example

kcp:
    tolerations:
      - key: "kcp"
        operator: "Equal"
        value: "true"
        effect: "NoSchedule"
    affinity:
      nodeAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 90
            preference:
              matchExpressions:
                - key: kcp
                  operator: In
                  values:
                    - "true"

Would result in a pod that has both affinity and toleration for the taint. I can create needed PR if this proposal is acceptable.

@embik
Copy link
Member

embik commented Apr 24, 2025

Hey @martivo, that sounds like a great addition to the Helm chart. Please feel free to submit a PR!

@martivo
Copy link
Author

martivo commented Apr 24, 2025

Please see #137

@martivo
Copy link
Author

martivo commented Apr 24, 2025

Will close once it is released and can confirmed that it solves issue.

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

No branches or pull requests

2 participants