rancher / rancher/support-bundle-kit
Depends on K8s and Rancher
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 43
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Description
Often times when issues are found and we need a log bundle, you can't deploy to the nodes in question. It would be good if Rancher ran a container or even an actual script loaded on the Node so that the user could manually collect a node's log bundle when K8s or Rancher are not operating. It seems to me that this tool depends on these two to be operational to deploy the log collecting daemonset.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the current daemonset-based log bundle collection path and reviewing how it depends on Kubernetes and Rancher. Define an offline node collection path that users can invoke when those services are unavailable, with completion shown by a usable node log bundle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100