Encrypt and manage SOPS-encrypted Kubernetes secrets in Flux GitOps workflows.
npx skills add https://github.com/saavy1/sb --skill managing-sops-secrets
Please help me install this Agent Skill. Skill: managing-sops-secrets Source: https://github.com/saavy1/sb/tree/main/docs/.claude/skills/managing-sops-secrets Command: npx skills add https://github.com/saavy1/sb --skill managing-sops-secrets
This Skill helps securely manage Kubernetes secrets in Flux GitOps workflows by encrypting them with SOPS and age-based keys, preventing plaintext exposure in the repository.
Encrypt a new secret for a Flux deployment and verify it can be decrypted correctly.
High-intent search queries and answers about installing and using this skill.
To encrypt Kubernetes secrets with SOPS for Flux GitOps, configure a .sops.yaml file with age-based keys. This encrypts data and stringData fields, preventing plaintext secret exposure in the repository while allowing Flux deployments to decrypt and synchronize them across clusters.
Flux fails to decrypt SOPS secrets when the .sops.yaml configuration is missing age keys or the encryption rules do not match. This Skill troubleshoots encryption and decryption issues by verifying the age key configuration and ensuring data and stringData fields are properly encrypted.
The best way to manage Flux GitOps secrets without plaintext is using SOPS with age-backed encryption. This approach encrypts secret data at rest in the repository and integrates with Flux to decrypt them during deployment across clusters, keeping secrets synchronized securely.
Yes, you can edit existing SOPS-encrypted secrets in a Flux deployment repository. This Skill supports decrypting and editing encrypted secrets, managing the .sops.yaml configuration for age keys, and verifying that the updated secrets can be decrypted correctly before applying them to clusters.
Yes, you need to configure age keys in a .sops.yaml file before encrypting secrets with SOPS for Kubernetes. This configuration defines the age-backed encryption keys and policy rules required to encrypt data and stringData fields and enables Flux to decrypt the secrets during GitOps deployments.
SOPS age encryption works with Flux by encrypting Kubernetes secrets at rest using age keys defined in .sops.yaml. Flux then decrypts these secrets during deployment, keeping clusters and superbloom secrets.yaml synchronized across the GitOps workflow without exposing plaintext in the repository.
nq-rdlEncrypt and decrypt YAML, JSON, ENV, and INI secrets with SOPS.
jrmatherlyProvide deployment and runtime context for Spacebot's Talos Kubernetes cluster.
keiretsu-labsDiagnose and manage Flux CD installations across multiple Kubernetes clusters.
rnavarychConfigure secrets management across HashiCorp Vault, AWS Secrets Manager, and GCP Secret Manager with Kubernetes injection and rotation policies.
