-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Feature Request] Add Support for Public ECR Gallery #1515
Comments
We would highly appreciate if we push this forward once Just to be aware, do we have any approximate timelines when Kaniko folks are planning to make the new release ? |
We have PR for fixing awslabs/amazon-ecr-credential-helper#248 awslabs/amazon-ecr-credential-helper#253 So next step should be collaborating with Kaniko folks for embedding latest ECR Credential Helper and cut new release. |
Thank you @PatrickXYS! |
Right, as long as the PR merged, we issue another PR in kaniko repo, and get it shipped. |
awslabs/amazon-ecr-credential-helper#253 has been merged and included in the latest 0.50 release. The next kaniko release will include it as it will be fetched during the docker build, I don't think we need a PR for that.
|
@theofpa Thanks for confirmation! How is it going with Kaniko folk's release cadence? |
Has this been included in kaniko v1.5.0-debug or is this slated for the next release? |
yes!
@PatrickXYS this issue can be closed as @tejal29 silently pushed v1.5.0 last week! |
Yeah very nice, we can close the issue as of now /close |
Given we have launched Public ECR registry last week, we should expect feature-requests fron ECR users for using Kaniko with Public ECR Authentication.
So the whole story will be:
Add support in amazon-ecr-credential-helper -> amazon-ecr-credential-helper cut new release -> Send PR to kaniko and make sure we build latest image of amazon-ecr-credential-helper into our executor image.
Related issue: awslabs/amazon-ecr-credential-helper#248
/cc @tejal29 @priyawadhwa
Any insights will be appreciated!
The text was updated successfully, but these errors were encountered: