Run any Skill in Manus with one click

ankra-helm-registries

Stars32

Forks2

UpdatedJuly 7, 2026 at 21:02

Connect HTTP and OCI Helm chart registries to Ankra and store least-privilege registry credentials (Harbor, Nexus, JFrog Artifactory, ChartMuseum, GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub). Use when the user needs charts from a private registry on a Kubernetes cluster, or mentions Helm registries, OCI registries, or registry credentials.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ankraio

ankraio/ankra-cli

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ankra-helm-registries
description	Connect HTTP and OCI Helm chart registries to Ankra and store least-privilege registry credentials (Harbor, Nexus, JFrog Artifactory, ChartMuseum, GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub). Use when the user needs private charts, mentions Helm registries, OCI registries, or registry credentials in Ankra.

Ankra Helm Registries

Addons pull charts from a repository_url. Public charts work as-is; private charts need a registry connected to Ankra with credentials.

Registry types

HTTP Helm repositories — classic chart servers: ChartMuseum, Harbor, Nexus, JFrog Artifactory, an S3-backed index. repository_url: https://charts.example.com.
OCI registries — charts stored as OCI artifacts: GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub. repository_url: oci://registry.example.com/charts.

Connect and use

Store a registry credential in Ankra (scoped, read-only where possible).
Reference the registry from the addon. Example with an OCI private chart:

addons:
  - name: my-app
    chart_name: my-app
    chart_version: 2.3.1
    repository_url: oci://ghcr.io/my-org/charts
    namespace: app
    # link the stored registry credential by name
    registry_credential_name: my-ghcr-credential

Manage registries and their credentials with the CLI:

ankra helm                      # manage Helm registries and registry credentials
ankra charts search <term>      # browse the chart catalog
ankra charts info <chart>       # inspect a chart and its versions

Rules

Least privilege. Registry credentials should be read-only pull tokens, scoped to the needed repositories.
Pin chart_version. Always pin; never resolve latest from a registry in production.
Prefer OCI for new private registries where the backend supports it.
Credentials live in Ankra, referenced by name from addons — never inline secrets in stack YAML.
Verify reachability from the cluster's network before relying on a private registry in a deploy.

Related skills

ankra-stacks-addons for the addon fields that consume a registry.
ankra-sops-secrets if a credential must be expressed as an encrypted manifest.

More from this repository

same repository

ankra-cloud-clusters

ankraio/ankra-cli

Provision and manage Ankra-managed Kubernetes clusters (K3s or kubeadm) on Hetzner Cloud, OVHcloud, UpCloud, and DigitalOcean - creating clusters, storing provider credentials, and managing node groups, scaling, Kubernetes versions, and upgrades. Use when the user wants to create or provision a new Kubernetes cluster (rather than import an existing one), or mentions Hetzner, OVH, UpCloud, or DigitalOcean clusters.

2026-07-0932

ankra-alerts-webhooks

ankraio/ankra-cli

Configure alerting and notifications for Kubernetes clusters through Ankra - alert rules and outbound webhooks that notify Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, Datadog, or custom endpoints, with automatic AI incident analysis attached to alerts. Use when the user wants alerting, notifications, incident routing, or on-call integration for a Kubernetes cluster in an Ankra environment.

2026-07-0732

ankra-cicd

ankraio/ankra-cli

Build CI/CD pipelines (GitHub Actions or GitLab CI) that deploy to Kubernetes the GitOps way - build a container image, push it with an immutable tag, and bump that tag in the Ankra GitOps repository so Ankra/ArgoCD syncs the change, rather than running kubectl/helm against the cluster from CI. Use when the user sets up CI/CD or automated deployment to a Kubernetes cluster in an Ankra environment, or asks how to deploy on push.

2026-07-0732

ankra-cli

ankraio/ankra-cli

Drive the Ankra CLI to log in, select an organisation and cluster, apply cluster/stack YAML, inspect pods, logs, events, and metrics, triage operations, and chat with Ankra AI. Use for day-to-day Kubernetes work whenever the `ankra` CLI is installed - checking what runs on a cluster, applying changes, debugging workloads, connecting kubectl - not only when the user names Ankra explicitly.

2026-07-0732

ankra-gitops

ankraio/ankra-cli

Structure a GitOps repository for Kubernetes with Ankra - modular include paths so cluster and stack definitions are stored in Git and synced by Ankra/ArgoCD. Use when the user sets up GitOps, connects a Git repository to a cluster, organizes cluster/stack YAML in a repo, or wants Git to be the source of truth for their Kubernetes configuration.

2026-07-0732

ankra-import-cluster

ankraio/ankra-cli

Author and apply an Ankra ImportCluster YAML manifest that connects an existing Kubernetes cluster (EKS, GKE, AKS, k3s, on-prem, ...) to the Ankra platform, wires a GitOps repository, and declares stacks of manifests and Helm addons with dependency ordering. Use when the user wants to import, onboard, or connect an existing Kubernetes cluster to a management platform, write a cluster.yaml / ImportCluster file, or apply one with `ankra cluster apply`.

2026-07-0732

name	ankra-helm-registries
description	Connect HTTP and OCI Helm chart registries to Ankra and store least-privilege registry credentials (Harbor, Nexus, JFrog Artifactory, ChartMuseum, GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub). Use when the user needs private charts, mentions Helm registries, OCI registries, or registry credentials in Ankra.

Ankra Helm Registries

Addons pull charts from a repository_url. Public charts work as-is; private charts need a registry connected to Ankra with credentials.

Registry types

HTTP Helm repositories — classic chart servers: ChartMuseum, Harbor, Nexus, JFrog Artifactory, an S3-backed index. repository_url: https://charts.example.com.
OCI registries — charts stored as OCI artifacts: GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub. repository_url: oci://registry.example.com/charts.

Connect and use

Store a registry credential in Ankra (scoped, read-only where possible).
Reference the registry from the addon. Example with an OCI private chart:

addons:
  - name: my-app
    chart_name: my-app
    chart_version: 2.3.1
    repository_url: oci://ghcr.io/my-org/charts
    namespace: app
    # link the stored registry credential by name
    registry_credential_name: my-ghcr-credential

Manage registries and their credentials with the CLI:

ankra helm                      # manage Helm registries and registry credentials
ankra charts search <term>      # browse the chart catalog
ankra charts info <chart>       # inspect a chart and its versions

Rules

Least privilege. Registry credentials should be read-only pull tokens, scoped to the needed repositories.
Pin chart_version. Always pin; never resolve latest from a registry in production.
Prefer OCI for new private registries where the backend supports it.
Credentials live in Ankra, referenced by name from addons — never inline secrets in stack YAML.
Verify reachability from the cluster's network before relying on a private registry in a deploy.

Related skills

ankra-stacks-addons for the addon fields that consume a registry.
ankra-sops-secrets if a credential must be expressed as an encrypted manifest.