ankra-cloud-clusters

Provision and manage Ankra-managed K3s clusters across Hetzner Cloud, OVHcloud, and UpCloud.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Provision brand-new clusters on Hetzner, OVHcloud, and UpCloud with managed credentials.
  • Manage cluster lifecycle (scale node groups, upgrade Kubernetes versions, and apply region/provider settings).
  • Store and reuse provider credentials and SSH keys for seamless cluster provisioning across providers.

Quick Start

Create a new cluster using ankra cluster <provider> create with the required credentials and region.

Frequently Asked Questions about ankra-cloud-clusters

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

FAQPage Schema
How do I provision a K3s cluster on Hetzner Cloud or OVHcloud?

Provision K3s clusters on Hetzner Cloud, OVHcloud, or UpCloud by executing provider-specific create commands with stored credentials and selected regions to launch managed nodes.

What is hybrid cloud K3s cluster management?

Hybrid cloud K3s cluster management provisions, scales, and upgrades lightweight Kubernetes clusters across multiple cloud providers while centrally storing and reusing provider credentials and SSH keys.

Can I store and reuse provider credentials for Kubernetes provisioning?

Store and reuse provider credentials and SSH keys for Kubernetes provisioning to enable seamless cluster creation and lifecycle management across Hetzner, OVH, and UpCloud.

How do I scale node groups and upgrade Kubernetes versions on existing clusters?

Scale node groups and upgrade Kubernetes versions by applying cluster lifecycle operations through provider-specific commands, allowing dynamic infrastructure adjustments and version management.

Does this approach support importing existing clusters or only provisioning new ones?

This approach supports provisioning brand-new clusters rather than importing existing ones, enforcing strict lifecycle management from initial creation on supported cloud providers.

When should I not use automated cloud provisioning for K3s clusters?

Avoid automated cloud provisioning when you need to import existing clusters or use providers outside Hetzner, OVHcloud, and UpCloud, as credential and lifecycle enforcement is provider-specific.