Improve handling of missing `--kubeconfig` when creating workload clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Summary
When creating workload only clusters using the CLI users need to specify the --kubeconfig parameter and provide the kubeconfig for the management cluster. When unspecified, providers can error in weird and wonderful ways. For example, the below logging is an error issued when creating Cloud Stack clusters.
2023-05-12T10:24:55.272-0500 V0 ❌ Validation failed {"validation": "cloudstack Provider
setup is valid", "error": "searching eksa CloudStackMachineConfigResponse: The connection to the ser
ver localhost:8080 was refused - did you specify the right host or port?\n", "remediation": ""}
This can make it difficult to understand what the problem is. This ticket is to track improvements around user feedback when the --kubeconfig is unspecified.
Contributor guide
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
Start from the CLI path that creates workload-only clusters and handles the --kubeconfig parameter; reproduce the missing-parameter case described in the issue. Trace where provider setup proceeds without the management-cluster kubeconfig, and define done as a clear user-facing validation message appearing before provider-specific connection errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100