kustomize-generators

Generate Kubernetes ConfigMaps and Secrets from literals, files, and environment data.

187|20|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill kustomize-generators
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kustomize-generators
Source: https://github.com/TheBushidoCollective/han/tree/main/jutsu/jutsu-kustomize/skills/kustomize-generators
Command: npx skills add https://github.com/TheBushidoCollective/han --skill kustomize-generators

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill demonstrates how to generate ConfigMaps and Secrets using Kustomize generators, including literals, files, and environment sources.

Core Features & Use Cases

  • ConfigMap/Secret Generators: Dynamic generation with content hashing.
  • File-Based & Env-Based: Generate from files or environment variables.
  • Named Generators: Avoid name collisions with proper naming.

Quick Start

Create a kustomization.yaml with a configMapGenerator and a secretGenerator for app settings.

Frequently Asked Questions about kustomize-generators

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

FAQPage Schema
How do I generate Kubernetes ConfigMaps and Secrets automatically with Kustomize?

Kustomize generators automate ConfigMap and Secret creation from literals, files, and environment variables by adding configMapGenerator and secretGenerator blocks to your kustomization.yaml. Kustomize automatically appends content hashes to resource names, triggering pod rollouts when configuration changes.

Can I generate ConfigMaps and Secrets from files and environment variables in the same Kustomize deployment?

Yes. Kustomize supports file-based, literal, and env-based inputs within a single kustomization.yaml. You can mix sources—loading files into ConfigMaps, environment variables into Secrets, and literal key-value pairs into either—all processed in one build.

How do I avoid ConfigMap and Secret name collisions when using Kustomize generators?

Use named generators with proper prefixing and suffixing in your kustomization.yaml. Kustomize appends content hashes to generated resource names, ensuring unique names across environments and preventing accidental overwrites in multi-environment CI/CD pipelines.

Do Kustomize generators support create, replace, and merge behaviors for ConfigMaps and Secrets?

Yes. Kustomize generators support multiple merge and override behaviors, allowing you to create new resources, replace existing ones, or merge configurations across overlays. This enables environment-specific customization without manual YAML editing in CI/CD workflows.

What's the difference between using Kustomize generators and manually writing ConfigMap and Secret YAML?

Kustomize generators eliminate manual YAML editing, automatically add content hashes for rollout triggering, and simplify multi-environment management. Manual YAML requires versioning names and orchestrating updates; generators handle this declaratively in kustomization.yaml.