Add more meaningful log messages when the cluster creation fails while waiting for control plane
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
Have better logs in case of failures due to something going wrong on the control plane node during cluster creation.
**Why is this needed**:
Currently, if something goes wrong on the workload cluster (image pull fails, pod errors out, etc.), the cli waits till the timeout and then errors out with [error waiting for workload cluster control plane to be ready](https://github.com/aws/eks-anywhere/blob/7fa7595f45bb86bae3f09f11bcfcf3b748446c22/pkg/clustermanager/cluster_manager.go#L320).
One thing we can do is that while the cli waits for control plane to be ready, it should also monitor the workload cluster for any issues/failures and report it back through the logs
Contributor guide
Research direction
Start at pkg/clustermanager/cluster_manager.go around line 320, where the CLI reports that it is waiting for the workload cluster control plane to be ready. Trace the cluster-creation wait path and determine how failures such as image-pull or pod errors can be surfaced; done means the CLI logs meaningful failure details instead of waiting only for the timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100