diff --git a/content/tutorials/esc-external-secret-operator/index.md b/content/tutorials/esc-external-secret-operator/index.md index a026de6fc157..a7b1e53c2ec9 100644 --- a/content/tutorials/esc-external-secret-operator/index.md +++ b/content/tutorials/esc-external-secret-operator/index.md @@ -39,40 +39,44 @@ prereqs: #### Install from Helm Chart Repository ```bash +# add ESO Operator Chart repo into helm helm repo add external-secrets https://charts.external-secrets.io helm repo update +# installs latest ESO Operator Chart, creates also namespace helm upgrade --install external-secrets external-secrets/external-secrets \ - --namespace external-secrets \ - --create-namespace \ - --wait + --namespace external-secrets \ + --create-namespace \ + --wait ``` #### Create secret containing Pulumi access token ```bash +# create a local k8s secret to store(PAT), to allow accessing Pulumi Cloud Resources kubectl create secret generic pulumi-access-token --from-literal=PULUMI_ACCESS_TOKEN=${PULUMI_ACCESS_TOKEN} \ --namespace external-secrets ``` #### Create ClusterSecretStore -Now you can create a [ClusterSecretStore](https://external-secrets.io/main/api/clustersecretstore/) resource that will tell External Secrets Operator to use Pulumi ESC as a secret provider. +You can create a [SecretStore](https://external-secrets.io/main/api/secretstore/) resource to notify the External Secrets Operator to use Pulumi ESC as a secret provider for a specific namespace. -If you want to limit the access by namespace, you can create a [SecretStore](https://external-secrets.io/main/api/secretstore/) resource instead, which is scoped to a single namespace. +However, if you want to expand the scope to an entire cluster you can use a [ClusterSecretStore](https://external-secrets.io/main/api/clustersecretstore/) resource instead. ```yaml cat <