Skip to content
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

[MRG] Add instructions for setting up an Azure Container Registry #878

Merged
merged 21 commits into from
Jun 16, 2019
Merged

[MRG] Add instructions for setting up an Azure Container Registry #878

merged 21 commits into from
Jun 16, 2019

Conversation

sgibson91
Copy link
Member

@sgibson91 sgibson91 commented Jun 13, 2019

Summary

This PR will add documentation around setting up and connecting an Azure Container Registry (ACR) to a BinderHub.

fixes #869

Changes Proposed in this PR

  • doc/setup-registry.rst - Azure command line instructions for creating an ACR, assigning the correct permissions and collecting relevant information have been added
  • doc/setup-binderhub.rst - templates for secret.yaml and config.yaml have been added to parse the information to BinderHub
  • An "Important" note box is added to the custom registry section of doc/setup-binderhub.rst to point out the hard dependency on the gcr.io image name structure.

@sgibson91 sgibson91 changed the title [WIP] Add instructions for setting up an Azure Container Registry [Ready for Review] Add instructions for setting up an Azure Container Registry Jun 13, 2019
where:

* `<ACR_NAME>` is the name you gave to your ACR,
* `<project-name>` is an arbitrary name that is required due to BinderHub's hard dependency on the `gcr.io` image structure above.
Copy link
Member

Choose a reason for hiding this comment

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

Can we replace "hard dependency" with "assumes that the image_prefix contains an extra level for the project name". We could fix this after all but so far haven't gotten round to it.

Do you think it would help people if we made a recommendation here as to what to use as a name? My recommendation would be to reuse <ACR_NAME>.

Copy link
Member Author

Choose a reason for hiding this comment

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

Changing the language 👍

It's tough to suggest a name as it has to be unique across all of Azure. So I ended up with testregistry1234sgibson91THISHADBETTERWORK before my test registry was deployed into a unique namespace 🙂 This is why I suggested the check-name function in the setup registry docs.

Copy link
Member

Choose a reason for hiding this comment

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

AH, I didn't mean to suggest a actual name name for ACR_NAME. I was thinking we should say that "a good value to use for <project-name> is the same value as you use for your <ACR_PROJECT>".

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, I see! Yeah that would work. I've personally gone with the name I gave to the BinderHub, so if there's multiple Hubs attached, you can see what came from where.

@betatim betatim changed the title [Ready for Review] Add instructions for setting up an Azure Container Registry [MRG] Add instructions for setting up an Azure Container Registry Jun 13, 2019
@betatim
Copy link
Member

betatim commented Jun 13, 2019

Looks excellent to me. I left one comment about "hard dependencies".

I didn't try and follow the instructions (no AZR account) but read the commands and didn't spot any obvious typos.

@sgibson91 sgibson91 merged commit 8b016ec into jupyterhub:master Jun 16, 2019
@sgibson91 sgibson91 deleted the docs/azure-registry branch June 16, 2019 14:49
yuvipanda pushed a commit to jupyterhub/helm-chart that referenced this pull request Jun 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How-to guide for setting up a private container repository
3 participants