Skip to content

Latest commit

 

History

History
27 lines (19 loc) · 1.79 KB

ContainerRegistry.md

File metadata and controls

27 lines (19 loc) · 1.79 KB

Plan Your Container Registry

This workshop requires that you have write access to a container registry. There are several places where registry credentials are required.

Examples of the values required for various container registries are as follows:

Registry Kpack Default Repository Cartographer Catalog Server Name Cartographer Catalog Repository
Azure Container Registry foo.azurecr.io/tce/kpack foo.azurecr.io tce
Dockerhub jeffgbutler/kpack index.docker.io jeffgbutler
Harbor harbor.tanzuathome.net/tce/kpack 1 harbor.tanzuathome.net tce
GitHub Container Registry ghcr.io/jeffgbutler/kpack ghcr.io jeffgbutler
Google Artifact Registry us-east1-docker.pkg.dev/foo/tce/kpack 2 us-east1-docker.pkg.dev foo/tce

Next (Install TCE Locally) ->

  • or -

Next (Install Guard Dog OVA) ->

Footnotes

  1. Harbor has the concept of projects in a repository. You must create the project in Harbor before pushing artifacts. In this case, we have a project named "tce"

  2. Google Artifact repository has two levels of naming - project-id, and repository. In this case we have project-id of "foo" (typically your GCP user name), and a repository named "tce". The repository must be created before pushing artifacts.