cluster-context

Provide deployment and runtime context for Spacebot's Talos Kubernetes cluster.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill cluster-context-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cluster-context
Source: https://github.com/jrmatherly/spacebot/tree/main/.claude/skills/cluster-context
Command: npx skills add https://github.com/jrmatherly/spacebot --skill cluster-context-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides authoritative deployment and runtime context for Spacebot's Talos Linux Kubernetes cluster so engineers make correct containerization, deployment, networking, storage, and secrets decisions without guessing cluster conventions or breaking GitOps workflows.

Core Features & Use Cases

  • Cluster architecture & stack: Describes OS, CNI, ingress, DNS, certificates, storage, and observability components used in production.
  • Flux GitOps & templating patterns: Explains the canonical app template, Jinja2 render pipeline, file layout, and the recommended distribution patterns for HelmRelease and OCIRepository usage.
  • Operational requirements: Lists required services, ports, PVC and health-check expectations, namespace layout, network policy constraints, and secrets/SOPS practices for deploying Spacebot.
  • Use Case Example: Use this reference when updating Spacebot's Dockerfile, HelmRelease values, or Flux templates to ensure compatibility with the ai namespace, LiteLLM routing, CNPG databases, and Envoy Gateway ingress.

Quick Start

Consult cluster-context before modifying Spacebot container images, Dockerfiles, HelmRelease values, or Flux templates to ensure deployments follow the Talos cluster patterns and namespace conventions.

Frequently Asked Questions about cluster-context

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

FAQPage Schema
How do I structure HelmRelease and Flux templates for a Talos Kubernetes cluster?

To structure HelmRelease and Flux templates for a Talos cluster, follow canonical GitOps patterns using a standard app template, Jinja2 render pipeline, and specific file layout for OCIRepository distribution. This ensures correct deployment without breaking workflows.

What namespace layout and networking constraints apply to deploying containers with Envoy Gateway and Cilium?

Deploying containers requires adhering to specific namespace layouts like ai, database, monitoring, and network, alongside Cilium network policy constraints and Envoy Gateway ingress rules. These define service endpoints, ports, and routing.

How does SOPS secret management integrate with Flux GitOps deployments?

SOPS secret management integrates with Flux GitOps by encrypting sensitive data at rest within the repository. The deployment context defines specific SOPS practices to ensure secrets are securely managed and rendered during the Jinja2 pipeline without exposing plaintext.

What storage and health-check expectations must I meet for PVCs in a Talos Linux deployment?

PVCs in a Talos Linux deployment must meet defined storage and health-check expectations to ensure application stability. The cluster context specifies required persistence configurations and liveness/readiness probes for services running across the designated namespaces.

Can I use standard Helm charts with LiteLLM routing and CNPG databases in this Kubernetes setup?

Standard Helm charts are compatible but must be adapted to the cluster's specific service integrations. Configurations need to account for LiteLLM routing rules, CNPG database connections, and the canonical HelmRelease values defined in the GitOps context.