secrets

Select Kubernetes secret provisioning mechanisms in a Flux GitOps environment.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill secrets-david-driscoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/secrets
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill secrets-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves confusion and misconfiguration when provisioning Kubernetes secrets across a GitOps cluster, helping you pick the correct mechanism and avoid broken secret syncs.

Core Features & Use Cases

  • Decision Tree for Secret Provisioning: Routes each secret to secret-generator, ExternalSecret, app-secrets, or kubernetes-replicator based on persistence, generation, and sharing requirements.
  • ExternalSecret Integration with AWS SSM: Applies the expected ClusterSecretStore pattern and SSM path convention for deterministic retrieval of externally managed values.
  • Cross-Namespace Secret Replication: Documents the correct source/consumer annotation pairing for kubernetes-replicator so multiple namespaces can share a single secret safely.
  • Debugging and Verification Workflow: Provides a script-driven workflow to inspect ExternalSecret and ClusterSecretStore health and surface common failure causes.

Quick Start

Ask the secrets skill which mechanism to use for a new application secret and request the manifest pattern that matches your persistence and sharing needs.

Frequently Asked Questions about secrets

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

FAQPage Schema
How do I manage Kubernetes secrets in a Flux GitOps environment?

To manage Kubernetes secrets in a Flux GitOps environment, use a decision tree to select the correct mechanism for generation, external sourcing, and cross-namespace sharing to avoid broken syncs. It routes secrets to the appropriate tool based on specific requirements.

How do I use ExternalSecret with AWS SSM in Kubernetes?

To use ExternalSecret with AWS SSM, apply the expected ClusterSecretStore pattern and follow the specific SSM path convention for deterministic retrieval of externally managed values. This ensures your ExternalSecret syncs correctly with SSM.

What is the best way to share a Kubernetes secret across multiple namespaces?

The best way to share a Kubernetes secret across multiple namespaces is using kubernetes-replicator. You must configure the correct source and consumer annotation pairing so multiple namespaces can safely share a single secret.

How do I debug Kubernetes ExternalSecret sync failures?

To debug Kubernetes ExternalSecret sync failures, use a script-driven workflow to inspect ExternalSecret and ClusterSecretStore health. This process surfaces common failure causes and verifies the sync status of your secrets.

When should I use a secret-generator versus ExternalSecret for app secrets?

Choose between a secret-generator and ExternalSecret by evaluating your secret's persistence and generation requirements. The decision tree routes secrets needing internal generation to secret-generator and externally managed values to ExternalSecret.