You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that there is an issue on our release v27 with pulling images from private ECR registries as the ecr-credential-provider binary is not being provided as part of the image anymore, more details in slack thread. This is currently blocking customers to upgrade to v27 and above.
Acceptance criteria:
Include ecr-credential-provider binary as part of our images
Draft releases for CAPA for all versions >v26.
Can we implement a regression test to ensure we won't hit a similar issue again?
The text was updated successfully, but these errors were encountered:
We can create a private registry in the same account and region we create the E2E clusters, upload a test image and then add a test where a Deployment is created pulling from the private registry.
It seems that there is an issue on our release v27 with pulling images from private ECR registries as the
ecr-credential-provider
binary is not being provided as part of the image anymore, more details in slack thread. This is currently blocking customers to upgrade to v27 and above.Acceptance criteria:
ecr-credential-provider
binary as part of our imagesThe text was updated successfully, but these errors were encountered: