Cloud / HELM Interview Questions
What is Helm OCI Registry support and how do you use it?
Helm v3 added support for storing charts in OCI (Open Container Initiative) registries, treating Helm charts as container artifacts alongside container images.
Enabling OCI support: OCI is experimental in early v3 but became stable in v3.8. Configure registry authentication: export HELM_EXPERIMENTAL_OCI=1 # v3.7 and earlier helm registry login myregistry.azurecr.io --username $REGISTRY_USERNAME --password $REGISTRY_PASSWORD
Saving chart to OCI registry: helm package ./mychart # creates mychart-0.1.0.tgz helm push mychart-0.1.0.tgz oci://myregistry.azurecr.io/helm
Installing chart from OCI registry: helm install myrelease oci://myregistry.azurecr.io/helm/mychart --version 0.1.0 Or using shorthand with dependency in Chart.yaml: dependencies: - name: mychart version: 0.1.0 repository: "oci://myregistry.azurecr.io/helm"
OCI vs HTTP repository comparison: - Authentication: OCI uses standard container registry auth (docker login) - Storage: OCI charts stored alongside images in the same registry - Versioning: OCI uses digest-based verification (sha256) - Layer caching: OCI supports layer caching for chart dependencies - Registry support: All major registries (ACR, ECR, GCR, Harbor, Docker Hub) support OCI artifacts
Listing and pulling charts: helm pull oci://myregistry.azurecr.io/helm/mychart --version 0.1.0 helm show chart oci://myregistry.azurecr.io/helm/mychart helm show values oci://myregistry.azurecr.io/helm/mychart
Best practices: Use OCI for organizations already using container registries. Keep chart versions unique (semver). Use registry lifecycle policies to clean old chart versions. For public charts, HTTP repositories (ArtifactHub) remain popular.
More Related questions...