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.
Currently, there's an inconsistency between the image paths for the EBS CSI driver in different registries:
provider-aws/aws-ebs-csi-driverebs-csi-driver/aws-ebs-csi-driverThis 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-awsrepository in ECR to eliminate these errors in testing and deployment scenarios.Additional context
See https://github.com/kubernetes/test-infra/pull/33061 for more context.
/priority/important-longterm