EXTENSIONS

Talos cluster lifecycle management via talm — init, configure, template nodes, apply configs, bootstrap, and health checks

Kubernetes operational toolkit — 17 model types covering pods, deployments, statefulsets, services, RBAC, storage, networking, autoscaling, batch jobs, External Secrets, and more. Includes 14 ready-to-run workflows for namespace debugging, security audits, RBAC analysis, cluster health, and operational diagnostics.

Install and operate a SHA-pinned k0s Kubernetes cluster on a Linux host over SSH, with a rendered k0s.yaml, readiness waits, kubeconfig capture, manifest stacks and Helm reconciliation. One model type serves any host: the SSH target and cluster inputs arrive per call, and state is keyed by the target host.

Install and operate a standalone Ceph cluster managed by cephadm on Debian-family Linux hosts reached over SSH. One model type drives host preparation, disk wiping, bootstrap, daemon placement, pools, CephFS, RGW users and buckets, maintenance and teardown.

Manage a Technitium DNS server or cluster: zones, records, block/allow lists, cache, diagnostics, settings backup and restore, and cluster membership. Written after rebuilding a live authoritative pair, and shaped by what that exposed. `record_ensure` is an idempotent upsert Technitium's own API cannot express — add fails on an existing record, update fails on an absent one — and it works for every record type including TLSA, because the read and write field names for TLSA, SSHFP and URI are not the same names and are mapped per type rather than renamed globally. `settings_backup` includes every section by default, so it produces a backup a server can actually be rebuilt from. `cluster_init`, `cluster_join` and `cluster_state` cover the membership a settings backup can never carry, alongside the TLS listener and certificate it also omits — the three things that make a restored node look broken.

A read-only inventory of a HashiCorp Nomad cluster from one call against the Nomad HTTP API: every job with its scheduling status and allocation rollup, every client node with its readiness and drain state, and cluster-wide health counts.

Full igor2 cluster-manager control via the REST API, split into five models: reservations (the reservation lifecycle), hosts (power, inventory, administration, host policies), boot (distros, profiles, images, kickstarts), identity (users, groups, privilege elevation), and server (clusters/MOTD, sync, stats, config, auth-reset, dashboard).