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

[BUG] Support bundle kit should respect node selector & taint toleration #5614

Closed
innobead opened this issue Mar 20, 2023 · 4 comments
Closed
Assignees
Labels
area/support-bundle Support bundle for troubleshooting area/upstream Upstream related like tgt upstream library backport/1.4.2 component/longhorn-manager Longhorn manager (control plane) kind/bug priority/0 Must be implement or fixed in this release (managed by PO) require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated severity/1 Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade)
Milestone

Comments

@innobead
Copy link
Member

innobead commented Mar 20, 2023

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

  • Longhorn version: 1.4.0/1.4.1
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
  • Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
    • Number of management node in the cluster:
    • Number of worker node in the cluster:
  • Node config
    • OS type and version:
    • CPU per node:
    • Memory per node:
    • Disk type(e.g. SSD/NVMe):
    • Network bandwidth between the nodes:
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
  • Number of Longhorn volumes in the cluster:

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.

@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Apr 10, 2023

Pre Ready-For-Testing Checklist

@longhorn-io-github-bot
Copy link

longhorn-io-github-bot commented Apr 13, 2023

Pre Ready-For-Testing Checklist

@c3y1huang
Copy link
Contributor

c3y1huang commented Apr 14, 2023

@yangchiu
Copy link
Member

yangchiu commented May 5, 2023

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.

@yangchiu yangchiu closed this as completed May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/support-bundle Support bundle for troubleshooting area/upstream Upstream related like tgt upstream library backport/1.4.2 component/longhorn-manager Longhorn manager (control plane) kind/bug priority/0 Must be implement or fixed in this release (managed by PO) require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated severity/1 Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade)
Projects
Status: Closed
Development

No branches or pull requests

4 participants