Try It Out
In this example we will deploy External Secrets Operator on a Kubernetes cluster using the Minimus External Secrets Operator Helm chart. The operator will manage syncing secrets from external secret management systems into Kubernetes.
Step 1: Start Cluster
If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions
Step 2: Create Namespace
Create a namespace:
kubectl create ns external-secrets
Step 3: Deploy the Helm Chart
Deploy the Minimus Helm chart:
helm install my-external-secrets oci://helm.mini.dev/external-secrets \
--version 2.5.0 \
-n external-secrets \
--wait
If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:
helm install my-external-secrets oci://helm.mini.dev/external-secrets \
--version 2.5.0 \
-f values.yaml \
-n external-secrets \
--wait
Step 4: Verify External Secrets Operator is Running
Confirm the chart deployed successfully and all pods are running:
kubectl get pods -n external-secrets
You should see output similar to:
NAME READY STATUS RESTARTS AGE
my-external-secrets-xxxxxxxxx-xxxxx 1/1 Running 0 2m
my-external-secrets-cert-controller-xxxxxxxxx-xxxxx 1/1 Running 0 2m
my-external-secrets-webhook-xxxxxxxxx-xxxxx 1/1 Running 0 2m
Step 5: Test Secret Syncing
Create a Fake SecretStore and an ExternalSecret to verify the operator is functioning:
cat <<EOF | kubectl apply -f -
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
name: test-store
namespace: external-secrets
spec:
provider:
fake:
data:
- key: /test/secret
value: hello-eso
version: "v1"
---
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: test-secret
namespace: external-secrets
spec:
refreshInterval: "0"
secretStoreRef:
name: test-store
kind: SecretStore
target:
name: test-result
data:
- secretKey: greeting
remoteRef:
key: /test/secret
version: "v1"
EOF
Wait for the ExternalSecret to sync:
kubectl wait --for=condition=Ready externalsecret/test-secret -n external-secrets --timeout=60s
Verify the synced secret value:
kubectl get secret test-result -n external-secrets -o jsonpath='{.data.greeting}' | base64 -d
You should see:
Step 6: Clean Up
Uninstall the chart and delete the namespace to remove all resources:
helm uninstall my-external-secrets -n external-secrets
kubectl delete namespace external-secrets
Terms & Info
Trademark
This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.
Disclaimer
Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.
