Add oci namespace validation for pulling eksa images
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**:
Add oci namespace validation for pulling eksa images. If specified, oci namespaces should have an entry for `public.ecr.aws`.
**Why is this needed**:
EKSA code expects an entry for `public.ecr.aws` in oci namespaces. Without this,https://github.com/aws/eks-anywhere/issues/6418 behavior gets triggered.
Contributor guide
Research direction
The issue names no files or tests. Start by tracing OCI namespace handling for EKS Anywhere image pulls and review the behavior referenced in issue #6418. Done means that when OCI namespaces are specified, validation requires an entry for public.ecr.aws and prevents the described behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100