proxmox-manager

Automate Proxmox cluster provisioning and Talos/Kubernetes lifecycle management.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/knowledgexhunta/devops-toolkit --skill proxmox-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proxmox-manager
Source: https://github.com/knowledgexhunta/devops-toolkit/tree/main/plugins/devops-toolkit/skills/proxmox-manager
Command: npx skills add https://github.com/knowledgexhunta/devops-toolkit --skill proxmox-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing Proxmox clusters, VM lifecycle, and Talos/Kubernetes bootstrap are complex and error-prone when done manually. This Skill provides a reproducible, policy-driven automation layer to streamline provisioning, upgrades, and teardown across multi-node environments.

Core Features & Use Cases

  • Deterministic VM provisioning and template management across a Proxmox cluster using a cluster-config.yaml backbone.
  • Talos/Kubernetes bootstrapping and upgrades integrated with Ansible, Flux, and Runbooks for end-to-end lifecycle management.
  • End-to-end lifecycle operations: cluster-create, cluster-teardown, node evacuation, Talos upgrades, and template recreation.

Quick Start

Spin up a staging Proxmox cluster using the talos-staging profile and verify all VMs reach a Ready state.

Frequently Asked Questions about proxmox-manager

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

FAQPage Schema
How do I automate Proxmox cluster provisioning and VM lifecycle management?

Automate Proxmox cluster provisioning by applying a policy-driven layer using cluster-config.yaml, REST API calls, and Taskfile workflows to ensure deterministic VM creation, template management, and consistent VMIDs across pve01, pve02, and pve03.

Can I use Ansible to bootstrap Talos and Kubernetes on a Proxmox cluster?

Bootstrap Talos and Kubernetes on Proxmox using integrated Ansible workflows that handle cluster creation, node evacuation, and end-to-end lifecycle upgrades driven by runbooks and a centralized cluster-config.yaml file.

What is the best way to manage multi-node Proxmox cluster templates consistently?

Manage multi-node Proxmox templates consistently by utilizing a cluster-config.yaml backbone that enforces deterministic VMIDs and standardized topology, enabling reproducible template recreation and VM provisioning across all nodes.

Does this Proxmox automation approach support node evacuation and cluster teardown?

Node evacuation and cluster teardown are fully supported through runbook-driven operations and Taskfile workflows, allowing safe removal of nodes and complete teardown of Talos/Kubernetes environments.

Do I need a cluster-config.yaml file to enforce RBAC and topology in Proxmox?

A cluster-config.yaml file is required to drive RBAC bootstrap, enforce consistent VMIDs, and maintain cluster topology across the Proxmox environment, ensuring reproducible and policy-driven operations.