Documentation
  • Getting Started
  • Creating a Product
    • Products Overview
    • Making a Helm Chart
      • Converting from docker-compose
      • Interpolated Values
      • Image Pull Secrets
      • Cluster Ingress
      • SSL Certificates
    • Setting up the Registry
      • Google Container Registry
  • Deploying a Product
    • Deployments Overview
    • Deploying on AWS
    • Deploying on GCP
    • Deploying on Azure (beta)
  • Debugging
    • GCP Permissions Errors
    • Volume Classes
Powered by GitBook
On this page
  1. Creating a Product

Setting up the Registry

PreviousSSL CertificatesNextGoogle Container Registry

Last updated 4 years ago

In order to run your Helm chart, your customer must be able to access your containers. A select group of people will opt to make their containers public and enforce usage requirements via license key or some other mechanism.

For vendors who cannot make their containers public, Metamanagement helps orchestrate access to the container registry, generating new credentials per customer which allows the vendor to selectively grant and revoke access as they see fit. Metamanagement currently only supports the for credential generation and distribution.

It is highly recommended that customers set up a new container registry for each new product. While Metamanagement can be granular in terms of determining who may access the registry, Metamanagement is incapable of being granular with respect to container access. If your customer should not have full unfettered access to your containers, we recommend creating new registries.

To get started with GCP, please continue to:

Google Container Registry
Google Container Registry