Use when working with Sealed Secrets — bitnami Sealed Secrets management for Kubernetes, certificate rotation, secret encryption, and controller health. Covers encrypting secrets for Git storage, certificate lifecycle management, namespace-scoped vs cluster-wide secrets, and controller diagnostics. Use when encrypting Kubernetes secrets for GitOps, rotating sealing keys, auditing sealed secrets, or troubleshooting the sealed-secrets controller.
Manage and analyze Bitnami Sealed Secrets, certificates, and controller health in Kubernetes.
kubeseal CLI and kubectl must be installed. The sealed-secrets controller must be running in the cluster.
#!/bin/bash
sealed_secrets_ns="${SEALED_SECRETS_NAMESPACE:-kube-system}"
sealed_secrets_controller="${SEALED_SECRETS_CONTROLLER:-sealed-secrets-controller}"
#!/bin/bash
echo "=== Sealed Secrets Controller ==="
kubectl get deployment "${sealed_secrets_controller}" -n "${sealed_secrets_ns}" -o json \
| jq '{name: .metadata.name, namespace: .metadata.namespace, replicas: .status.readyReplicas, available: .status.availableReplicas, image: .spec.template.spec.containers[0].image}'
echo ""
echo "=== Controller Pod Status ==="
kubectl get pods -n "${sealed_secrets_ns}" -l "app.kubernetes.io/name=sealed-secrets" -o json \
| jq -r '.items[] | "\(.metadata.name)\t\(.status.phase)\t\(.status.containerStatuses[0].restartCount) restarts"' | column -t
echo ""
echo "=== Active Sealing Key ==="
kubeseal --fetch-cert --controller-name="${sealed_secrets_controller}" --controller-namespace="${sealed_secrets_ns}" 2>/dev/null \
| openssl x509 -noout -dates 2>/dev/null || echo "Could not fetch certificate"
#!/bin/bash
NAMESPACE="${1:-}"
echo "=== Sealed Secrets ==="
if [ -n "$NAMESPACE" ]; then
kubectl get sealedsecrets -n "$NAMESPACE" -o json
else
kubectl get sealedsecrets --all-namespaces -o json
fi | jq -r '.items[] | "\(.metadata.namespace)\t\(.metadata.name)\t\(.metadata.creationTimestamp[0:16])"' \
| column -t | head -25
#!/bin/bash
echo "=== Sealing Keys ==="
kubectl get secrets -n "${sealed_secrets_ns}" -l "sealedsecrets.bitnami.com/sealed-secrets-key=active" -o json \
| jq -r '.items[] | "\(.metadata.name)\t\(.metadata.creationTimestamp[0:16])\tactive"' | column -t
echo ""
echo "=== Certificate Expiry ==="
kubeseal --fetch-cert --controller-name="${sealed_secrets_controller}" --controller-namespace="${sealed_secrets_ns}" 2>/dev/null \
| openssl x509 -noout -subject -dates 2>/dev/null
echo ""
echo "=== Key Rotation History ==="
kubectl get secrets -n "${sealed_secrets_ns}" -l "sealedsecrets.bitnami.com/sealed-secrets-key" -o json \
| jq -r '.items | sort_by(.metadata.creationTimestamp) | .[] | "\(.metadata.name)\t\(.metadata.creationTimestamp[0:16])"' | column -t
#!/bin/bash
echo "=== Sealed Secrets by Namespace ==="
kubectl get sealedsecrets --all-namespaces -o json \
| jq -r '.items[] | .metadata.namespace' | sort | uniq -c | sort -rn | head -15
echo ""
echo "=== Recently Modified ==="
kubectl get sealedsecrets --all-namespaces -o json \
| jq -r '.items | sort_by(.metadata.creationTimestamp) | reverse | .[0:10][] | "\(.metadata.namespace)\t\(.metadata.name)\t\(.metadata.creationTimestamp[0:16])"' \
| column -t
column -t--help output.| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
--scope flag to changekube-system but may vary -- check SEALED_SECRETS_NAMESPACEstrict (default, namespace+name bound), namespace-wide, cluster-wide