Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 1.5 KB

002-chart-registry-repo.md

File metadata and controls

23 lines (17 loc) · 1.5 KB

Helm Charts Align With Registry Repositories

Container images are referneced with a multi-part URL:

  • [login url] / [namespace] / [repo] : [tag]
  • [namespace] / [repo] : [tag ] are equally referred to as an "image"

Different clouds implement the unique login url in a few different forms, while effectively meaning the same thing:

Cloud Format eg: image
Docker Hub [org|user ] / [image] : [tag] *1 contoso/marketing-fall2018-web:aab1
Azure Container Registry (acr) [uniqueId].azurecr.io / [namespace] / [image] : [tag] contoso.azurecr.io/marketing/fall2018/web:aab1
Google Container Registry (gcr) gcr.io/[uniqueId] / [image] : [tag] gcr.io/marketing/fall2018-web:aab1
AWS Container Registry (ecr) [aws_account_id].dkr.ecr.region.amazonaws.com/ [image] : [tag] 123abc456def.dkr.ecr.region.amazonaws.com/marketing/fall2018-web:aab1
  1. Docker Hub has a default login url docker.io
  2. Docker Hub [org|user ] is a [namespace] which is currently limted to two nodes.
    The Microsoft Container Registry (mcr) has implemented a syndicated catalog representing a product hierarchy within the docker store, and looks for Docker to expand this for other partners with deep image catalogs.

Helm References

Proposal aligns Helm Charts with the same referencing scheme:

  • [login url] / [namespace] / [chart] : [version/tag]