Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align ECR image path with Kubernetes community registry #2096

Open
torredil opened this issue Jul 23, 2024 · 0 comments
Open

Align ECR image path with Kubernetes community registry #2096

torredil opened this issue Jul 23, 2024 · 0 comments
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@torredil
Copy link
Member

Currently, there's an inconsistency between the image paths for the EBS CSI driver in different registries:

  • KCR: registry.k8s.io/provider-aws/aws-ebs-csi-driver
  • ECR: public.ecr.aws/ebs-csi-driver/aws-ebs-csi-driver

This discrepancy causes issues in testing environments that use registry mirroring or substitutions.

In the long term, it would be desirable to align the ECR path with the community registry by migrating to a provider-aws repository in ECR to eliminate these errors in testing and deployment scenarios.

Additional context

See kubernetes/test-infra#33061 for more context.

/priority/important-longterm

@torredil torredil added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

1 participant