-
Notifications
You must be signed in to change notification settings - Fork 389
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
Support dynamic registry tokens, add wrapper for working with registry microservice #1637
Conversation
3fbfe6b
to
b3682df
Compare
06f105e
to
c38e5f3
Compare
0b1eba8
to
53fe226
Compare
53fe226
to
b92fdfb
Compare
Anyone else have thoughts on this? @stevejpurves is interested in using it. |
@yuvipanda do you have any thoughts on this? |
This has been ready for 6 months, and it's effectively been in production (though being overriden in https://github.com/jupyterhub/mybinder.org-deploy/blob/b9439b5b15263ff703ea46c07bfd6c4584d1422c/config/curvenote.yaml#L59-L148) so merging! |
jupyterhub/binderhub#1637 Merge pull request #1637 from manics/registry-dynamic-token
Sorry for dropping this @manics! Happy for you to have merged this! |
This is a companion for jupyterhub/repo2docker#1245 that allows dynamic credentials t be used for pushing to a registry. This is required for e.g. ECR where the token used to login to the reigistry expires.
This also implements the non-vendor specific parts of
#1623
Closes #705
You can see an example implementation of the microservice side in
https://github.com/manics/binderhub-container-registry-helper
This is working with AWS ECR using an IRSA role for the microservice.
It's written in Go as I wanted to learn it, but if we choose to pursue this rewriting it in Python (or Javascript, or any other language) shouldn't be too difficult.