Validate whether registry mirror is public in preflight validations
Open
area/airgap
area/cli
kind/cleanup
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
If the registry mirror provided is not set to public, we throw an error saying that it is unauthorized. For the create flow, it would be better if we throw an error in the preflight validations to fail fast instead of fail later in the flow.
Contributor guide
Research direction
Start by locating the preflight validations in the create flow and trace how the registry mirror is checked. Confirm the current unauthorized failure path, then verify that a non-public mirror is rejected during preflight rather than later in cluster creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100