ankra-helm-registries

Connect private Helm registries to Ankra with least-privilege credentials.

26|2|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/ankraio/ankra-cli --skill ankra-helm-registries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ankra-helm-registries
Source: https://github.com/ankraio/ankra-cli/tree/main/internal/skills/embedded/skills/ankra-helm-registries
Command: npx skills add https://github.com/ankraio/ankra-cli --skill ankra-helm-registries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connects private Helm registries to Ankra and manages least-privilege credentials for chart pulls.

Core Features & Use Cases

  • Connect HTTP Helm repositories such as ChartMuseum, Harbor, Nexus, and Artifactory with a centralized credential store.
  • Manage OCI registries like GHCR, ECR, and Google Artifact Registry with read-only access tokens.
  • Use case: teams deploying private charts in Kubernetes clusters can reference stored credentials to pull charts securely.

Quick Start

Connect a private Helm registry to Ankra by storing a read-only credential and referencing it from an addon.

Frequently Asked Questions about ankra-helm-registries

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect a private Helm registry to Kubernetes deployments?

To connect private Helm registries to Kubernetes, store read-only credentials in a centralized store and reference them from addons to securely pull charts during deployments.

Can I use OCI registries like GHCR and ECR to pull private Helm charts?

Yes, OCI registries including GHCR, ECR, and Google Artifact Registry are supported for pulling private Helm charts using managed read-only access tokens.

What HTTP Helm repositories are supported for private chart management?

HTTP Helm repositories such as ChartMuseum, Harbor, Nexus, and Artifactory are supported for managing private chart credentials through a centralized credential store.

How does least-privilege access work for Helm chart pulls?

Least-privilege access for Helm chart pulls is enforced by applying read-only credentials from Ankra, ensuring deployment teams can only pull charts without broader registry permissions.

Do I need Ankra credential management to pull private Helm charts in Kubernetes?

Yes, Ankra credential management is required to store and reference the read-only access tokens needed for securely pulling private Helm charts in Kubernetes environments.

Why use a centralized credential store for private Helm registries?

A centralized credential store for private Helm registries allows teams deploying private charts in Kubernetes clusters to securely reference stored credentials instead of managing secrets individually.