rancher / rancher/support-bundle-kit
Doc: add simulator limitation and common pitfalls
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 43
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Description
When examining a support bundle with the simulator, there are some simulator-made changes, we need to document this in case engineers feel misleading.
- node taints.
- Node will always have the taint:
taints: - effect: NoSchedule key: node.kubernetes.io/not-ready
- Node will always have the taint:
- uid is different. Simulator generates new uids when loading resources.
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
No documentation file or test is named in the issue. Start by locating the simulator and support-bundle documentation, then document the simulator-added node.kubernetes.io/not-ready taint and regenerated resource UIDs; done means engineers are warned about both differences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100