Higher verbosity for EKS Anywhere System Pods in Bootstrap Cluster
Open
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**: I would like to have more log verbosity for EKS Anywhere system pods, such as capt, capv, tinkerbell stack and cluster API
**Why is this needed**: More data for troubleshooting when things went wrong
Contributor guide
Research direction
No source files or tests are identified. Begin by locating the bootstrap-cluster configuration and logging entry points for capt, capv, the Tinkerbell stack, and Cluster API; done means those system pods expose higher verbosity that supplies more troubleshooting data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100