Skip to content

Enable awsecr-creds addon #901

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

Merged
merged 1 commit into from
Dec 9, 2016

Conversation

stevesloka
Copy link
Contributor

This addon will automatically setup credentials to allow for minikube to pull images from an ECR docker registry running on AWS.

It requires a secret to be created to function. That secret contains the AWS_ACCESS_ID, AWS_SECRET_ACCESS_KEY as well as the AWS Account Id.

This resolves #366

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 9, 2016
@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@codecov-io
Copy link

Current coverage is 33.12% (diff: 100%)

Merging #901 into master will not change coverage

@@             master       #901   diff @@
==========================================
  Files            43         43          
  Lines          1899       1899          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            629        629          
  Misses         1150       1150          
  Partials        120        120          

Powered by Codecov. Last update a9bfc57...7e989d1

@r2d4
Copy link
Contributor

r2d4 commented Dec 9, 2016

@minikube-bot ok to test

@@ -0,0 +1,44 @@

Copy link
Contributor

@r2d4 r2d4 Dec 9, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if its exactly needed on these yamls since it passed our boilerplate test - but the K8s Copyright Header is missing here

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore this comment - it isn't enforced upstream on k8s either

@aaron-prindle
Copy link
Contributor

It can be in a different PR but I think that addons which require additional setup (the inclusion of the secrets file) should have a callback that outputs instructions to the user.

@stevesloka
Copy link
Contributor Author

@aaron-prindle I can do the additional step as a 2nd PR

@dlorenc
Copy link
Contributor

dlorenc commented Dec 9, 2016

This LGTM, we can follow up with the help text.

@stevesloka
Copy link
Contributor Author

Awesome thanks @aaron-prindle & @r2d4 I'll get to work on the next PR for the help text next.

@dlorenc dlorenc merged commit 8bc094f into kubernetes:master Dec 9, 2016
@ghostsquad
Copy link

Sorry to resurrect an old PR, but does anyone think this is kinda sketchy? There's 0 transparency about what this image/container actually does:
https://hub.docker.com/r/upmcenterprises/registry-creds/

No description, it's not an automated build from a public github repo either.

@aaron-prindle
Copy link
Contributor

@ghostsquad
Repo for the addon is here:
https://github.com/upmc-enterprises/registry-creds

@stevesloka stevesloka deleted the awsecr-creds-addon branch February 9, 2018 18:24
@ghostsquad
Copy link

ghostsquad commented Feb 12, 2018

@aaron-prindle thanks. I'm contributing to that repo to help increase the transparency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How to pull images from ECR?
9 participants