---
name: "kubernetes-external-secrets-operator"
description: "Synchronize secrets securely from AWS Secrets Manager, Vault, and GCP into Kubernetes Secrets."
metadata:
  author: "External Secrets"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "sync aws secrets manager to k8s"
  - "configure external secrets operator"
  - "vault to k8s secrets"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# External Secrets Operator (ESO) Multi-Cloud Sync

Configures External Secrets Operator (ESO): setting up SecretStore and ClusterSecretStore resources, mapping external secret keys, defining refreshInterval, and converting JSON secret payloads into native K8s Secrets.

## When to Invoke
Invoke this skill whenever you need to:
- sync aws secrets manager to k8s
- configure external secrets operator
- vault to k8s secrets

## Execution SOP & Rules
1. Install ESO via Helm: helm install external-secrets external-secrets/external-secrets.
2. Create SecretStore specifying provider (aws, vault, gcp) and authentication serviceAccountRef.
3. Define ExternalSecret resource specifying target secret name and remoteRef keys.
4. Verify synchronization: kubectl get externalsecrets to check status Ready=True.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.