kcli

Automate multi-provider VM management and infrastructure orchestration via a single CLI.

649|170|Updated Sep 2, 2016
One-click install
npx skills add https://github.com/karmab/kcli --skill kcli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcli
Source: https://github.com/karmab/kcli/tree/main/.claude/skills/kcli
Command: npx skills add https://github.com/karmab/kcli --skill kcli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

kcli provides a single command-line interface to deploy and manage VMs, networks, plans, Kubernetes clusters, and more across multiple providers, simplifying multi-environment administration.

Core Features & Use Cases

  • Unified multi-provider VM management: create, list, info, start, stop, delete across Libvirt, AWS, GCP, Azure, vSphere, OpenStack, and more.
  • Plan-driven infrastructure: YAML templates with Jinja templating to deploy complex environments.
  • Profiles for reusable VM templates and consistent configurations.

Quick Start

Install and run kcli to start managing your infrastructure.

Frequently Asked Questions about kcli

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

FAQPage Schema
How do I manage VMs across multiple infrastructure providers using a single CLI?

Multi-provider VM management is handled through a unified CLI interface that supports creating, listing, starting, stopping, and deleting instances across Libvirt, AWS, GCP, Azure, vSphere, and OpenStack. This eliminates the need for provider-specific command-line tools.

Can I use declarative YAML plans for cross-provider infrastructure orchestration?

Declarative YAML plans support Jinja templating to orchestrate complex environments across diverse providers. This plan-driven approach ensures consistent infrastructure deployments from VM creation through deletion.

Does this tool support deploying Kubernetes clusters across different cloud providers?

Kubernetes clusters can be deployed and managed across diverse providers using the unified CLI. It handles end-to-end operations, enabling consistent cluster provisioning regardless of the underlying infrastructure environment.

How do reusable profiles help with consistent VM template configurations?

Profiles act as reusable VM templates to maintain consistent configurations across deployments. They simplify multi-environment administration by standardizing instance settings before creation.

What is the best way to automate end-to-end VM operations from creation to deletion?

Automating end-to-end VM operations is achieved via robust CLI workflows that execute plan-driven deployments. This provides a single interface to manage the entire lifecycle of virtual machines across supported providers.

Are there limitations when orchestrating infrastructure across diverse cloud platforms?

Cross-provider orchestration relies on the unified CLI's compatibility with each specific provider's API. Limitations depend on the underlying support for Libvirt, AWS, GCP, Azure, vSphere, and OpenStack features within the tool.