@@ -60,6 +60,11 @@ need to insert. Note that the first line is not indented at all::
60
60
"client_x509_cert_url": "<REPLACE>"
61
61
}
62
62
63
+ If you are using Google Artifact Registry
64
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
65
+
66
+ You do not need to do anything.
67
+
63
68
If you are using Docker Hub
64
69
~~~~~~~~~~~~~~~~~~~~~~~~~~~
65
70
@@ -179,6 +184,34 @@ your ``config.yaml`` file::
179
184
* Note that in both cases, you should remove the ``< `` and ``> `` symbols,
180
185
they are simply placeholders in the code above.
181
186
187
+ If you are using Google Artifact Registry
188
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
189
+
190
+ To configure BinderHub to use Google Artifact Registry, add the following to your `config.yaml ` file::
191
+
192
+ config:
193
+ BinderHub:
194
+ use_registry: true
195
+ image_prefix: <region>-docker.pkg.dev/<google-project-id>/<prefix>-
196
+ registry_class: "binderhub.registry.GoogleArtifactRegistry"
197
+ DockerRegistry:
198
+ url: "https://<region>-docker.pkg.dev"
199
+ token_url: "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/<service-account-name>/token"
200
+
201
+ .. note ::
202
+
203
+ * ``<region> `` This is the region of the Artifact Registry repository, such
204
+ as ``us-central1 ``.
205
+ * ``<google-project-id> `` This is the project *ID *, which may be different
206
+ from the project *name *.
207
+ * ``<prefix> `` can be any string, and will be prepended to image names. We
208
+ recommend something descriptive such as ``binder-dev- `` or ``binder-prod- ``
209
+ (ending with a `- ` is useful).
210
+ * ``<service-account-name> `` This is the name of the service account the
211
+ node pool is configured to use.
212
+ * Note that in all cases, you should remove the ``< `` and ``> `` symbols,
213
+ they are simply placeholders in the code above.
214
+
182
215
If you are using Docker Hub
183
216
~~~~~~~~~~~~~~~~~~~~~~~~~~~
184
217
0 commit comments