k8s-config

Manage Kubernetes ConfigMaps and SealedSecrets with a git-first workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nirssyan/nirssyan-mono --skill k8s-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-config
Source: https://github.com/nirssyan/nirssyan-mono/tree/main/.cursor/skills/k8s-config
Command: npx skills add https://github.com/nirssyan/nirssyan-mono --skill k8s-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the management of Kubernetes configurations, specifically ConfigMaps for LLM models and SealedSecrets for API keys, by enforcing a git-first workflow. It helps prevent configuration drift and ensures secure handling of sensitive information.

Core Features & Use Cases

  • Git-First Workflow: Ensures all changes are version-controlled before being applied to the cluster.
  • Secure Secret Management: Handles API keys via SealedSecrets, preventing direct exposure of sensitive values.
  • Model Configuration: Manages LLM model configurations within ConfigMaps.
  • Use Case: When updating an AI agent's LLM model or rotating an API key, use this Skill to update the configuration in Git, apply it to the Kubernetes cluster, and restart the relevant services.

Quick Start

Use the k8s-config skill to set the 'view' model to 'haiku' in the development environment.

Frequently Asked Questions about k8s-config

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

FAQPage Schema
How do I manage Kubernetes ConfigMaps for LLM models using a git-first workflow?

Managing Kubernetes ConfigMaps for LLM models through a git-first workflow involves version-controlling configuration changes in Git before applying them to the cluster. This enforces a strict git-first workflow to prevent configuration drift across development and production environments.

What's the best way to secure API keys in Kubernetes without exposing sensitive values?

Securing API keys in Kubernetes without exposing sensitive values is achieved using SealedSecrets. This approach encrypts sensitive data at the Git repository level, ensuring direct exposure of API keys is prevented before being decrypted and applied to the cluster.

Do I need kubeseal and kubectl installed to manage K8s SealedSecrets?

Yes, you need kubeseal and kubectl installed to manage K8s SealedSecrets. This Skill requires kubectl for cluster interaction and kubeseal for encrypting secrets, alongside the git CLI to maintain the required git-first workflow.

How do I update an LLM model configuration in Kubernetes development and production environments?

Updating an LLM model configuration in Kubernetes environments involves modifying the ConfigMap in a Git repository, applying the committed changes via kubectl, and restarting the relevant services. This workflow manages cluster state across development and production.

Why enforce a git-first workflow for Kubernetes configuration management?

Enforcing a git-first workflow for Kubernetes configuration management prevents configuration drift and ensures secure handling of sensitive information. By version-controlling ConfigMaps and SealedSecrets before cluster application, all changes are reliably tracked.