Installing External Secrets Operator
What you'll learn: How to deploy External Secrets Operator (ESO) to your Kubernetes cluster using Helm and verify it's running correctly.
The Core Idea
Now that you understand ESO's architecture, it's time to actually install it. The standard installation method uses Helm, which deploys two critical components: a controller that watches for ExternalSecret resources and syncs them, and a webhook that validates your configurations before they're applied.
Think of it like installing a translator service at a border crossing—the controller is the translator booth that actively converts foreign documents into local forms, while the webhook is the checkpoint that ensures documents are properly formatted before letting them through.
Installing ESO via Helm
First, add the External Secrets Helm repository:
helm repo add external-secrets https://charts.external-secrets.io
helm repo update
Then install ESO into the external-secrets namespace:
helm install external-secrets \
external-secrets/external-secrets \
--namespace external-secrets \
--create-namespace
Validating the Installation
Check that the controller and webhook pods are running:
kubectl get pods -n external-secrets
You should see output similar to:
NAME READY STATUS
external-secrets-5d8c9b4f8-xyz12 1/1 Running
external-secrets-webhook-6c7b8d9f5-abc34 1/1 Running
external-secrets-cert-controller-7f6d8c5-def56 1/1 Running
The controller deployment watches for ExternalSecret resources and reconciles them. The webhook deployment validates SecretStore and ExternalSecret manifests before admission. The cert-controller manages webhook certificates.
Key Takeaway: Installing ESO via Helm deploys controller and webhook components that work together to validate and synchronize external secrets—verify both are running before creating ExternalSecret resources.