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

Support to configure tolerations for consul-cni Daemonset #3367

Open
posquit0 opened this issue Dec 13, 2023 · 3 comments
Open

Support to configure tolerations for consul-cni Daemonset #3367

posquit0 opened this issue Dec 13, 2023 · 3 comments
Labels
type/enhancement New feature or request

Comments

@posquit0
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Is your feature request related to a problem? Please describe.

  • consul-cni Pod couldn't scheduled into nodes with NoSchedule taints.

Feature Description

  • Support to configure tolerations for consul-cni Daemonset like consul-client.

Use Case(s)

  • Override tolerations for consul-cni Pod for nodes with NoSchedule taints.

Contributions

No

@posquit0 posquit0 added the type/enhancement New feature or request label Dec 13, 2023
@posquit0 posquit0 changed the title Support to confirue tolerations for consul-cni Daemonset Support to configure tolerations for consul-cni Daemonset Jan 22, 2024
@posquit0
Copy link
Author

posquit0 commented Feb 2, 2024

My organization is experiencing a lot of frustration. Please look into it.

@david-yu
Copy link
Contributor

david-yu commented Feb 2, 2024

Thanks @posquit0 for your feedback. We haven't prioritized this issue yet and likely won't work on this until after Consul 1.18 GA. But I agree this is a valid feature request.

@posquit0
Copy link
Author

Is there any plan to support this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants