-
Notifications
You must be signed in to change notification settings - Fork 592
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
[BUG] Support bundle kit should respect node selector & taint toleration #5614
Comments
Pre Ready-For-Testing Checklist
|
Pre Ready-For-Testing Checklist
|
|
Verified passed on master-head (support-bundle-kit v0.0.24). The support bundle kit test cases for node selector and taint toleration can pass, and recently there's no support bundle downloading issue in daily regression. |
Describe the bug (🐛 if you encounter this issue)
It seems there are no node selectors or taint toleration passed to the support bundle kit, so it will cause deploying a support bundle agent in any node in the cluster. Currently, the image only supports arm64/amd64/s390x, so any non-supported arch nodes will have a pending pod to cause the support bundle kit agent daemonset unable to start successfully.
Need to respect the same node selector & taint toleration for system management components.
To Reproduce
#5613 (comment)
Expected behavior
A clear and concise description of what you expected to happen.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment
Additional context
cc @longhorn/qa for any system management components (instance manager, share manager, backing image, support bundle kit manager), need to verify pod deployment use cases.
The text was updated successfully, but these errors were encountered: