ข้ามไปยังเนื้อหา
เอกสารคู่มือ

This is the Experimental version (Latest). It is under active development and may change. For the most reliable documentation, use the version selector in the top-right to switch to Stable, or click here to go to the Stable version's homepage.

External Secrets Operator (ESO) Installation

อัพเดทล่าสุด:

เนื้อหานี้ยังไม่มีในภาษาของคุณ

External Secrets Operator (ESO) is a Secret Syncing from Vault to Kubernetes Cluster as Kubernetes Secret Resource Utility

External Secrets Operator (ESO) can have multiple instances dedicated to each of Workload Type Kubernetes Cluster.

Pre-Installation

Section titled “Pre-Installation”

ESO Preparation

Section titled “ESO Preparation”

  1. Create Helm Value Configurations

    Terminal window
    cat <<EOF > $BASE_WORKING_DIR/helm-values/eso-full-values.yaml
    leaderElec: true
    installCRDs: true
    

    EOF

Installation

Section titled “Installation”

  1. Add ESO Helm Repository.

    Terminal window
    # Add Helm Repository
    helm repo add external-secrets-operator https://charts.external-secrets.io/
    helm repo update

  2. Connect to Kubernetes Cluster ; i.e w/ Kubeconfig File

    Terminal window
    source $BASE_WORKING_DIR/shell-values/kubernetes/CHANGEME_cluster.vars.sh

  3. Install ESO on Kubernetes Cluster.

    • Install a Helm Release with specific Helm Chart Version --version 0.19.2 (App Version: v0.19.2)

      Terminal window
      # Install ESO Helm Release
      helm upgrade --install external-secrets-operator external-secrets-operator/external-secrets --version 0.19.2 \
          --namespace devsecops-system \
          -f $BASE_WORKING_DIR/helm-values/eso-full-values.yaml

Post-Installation

Section titled “Post-Installation”

External Secrets Operator (ESO) Testing

Section titled “External Secrets Operator (ESO) Testing”

  1. Connect to Kubernetes Cluster ; i.e w/ Kubeconfig File

    Terminal window
    source $BASE_WORKING_DIR/shell-values/kubernetes/CHANGEME_cluster.vars.sh

  2. Get Pod Status - External Secret Operator (ESO)

    Terminal window
    kubectl get pods -n devsecops-system

    External Secret Operator (ESO) should be `Running

    NAME                   READY   STATUS    RESTARTS   AGE
    ... (deducted)
    external-secret-operator-external-secrets-XXXXXXX-YYYY            1/1     Running   0          XdXh
    external-secret-operator-external-secrets-cert-controller-YYYYY   1/1     Running   0          XdXh
    external-secret-operator-external-secrets-webhook-XXXXXXXXX       1/1     Running   0          XdXh

Finished?

Use the below navigation to proceed