SKIP UPDATE CHECK "Create cluster secrets based off of provided user value targets"

General MR

Summary

This merge request addresses the implementation of external-secret-operator to create cluster-level secrets based on user-defined targets specified in the values.yaml file. Each target described in the configuration will have a corresponding cluster secret created in Kubernetes.

Relevant logs/screenshots

Here is the values override used showing how the targets are defined.

secretConfiguration:
  enabled: true
  secretList:
    - name: sc-es
      namespace: default
      source:
        provider: aws
        service: SecretsManager
        region: "us-gov-west-1"
        refreshInterval: "1m"
        auth:
          authType: "accesskey"
          accessKeyName: "chu-awssm-secret"
          accessKeyID: "access-key"
          secretAccessKey: "secret-access-key"
          serviceAccount: ""
        secrets:
          targetName: "sc-key"
          targetPolicy: ""
          secretKeyName:
            key: target-secret
            version: "1"
            property: ""

chuka@DESKTOP-006TSPC:~/external-secrets/external-secrets$ kubectl get externalsecret -n default
NAME                    STORE                      REFRESH INTERVAL   STATUS         READY
sc-es-externalsecrets   sc-es-clustersecretstore   1m                 SecretSynced   True

kubectl get secrets -n default produces the created key "sc-key" from the values

chuka@DESKTOP-006TSPC:~/external-secrets/external-secrets$ kubectl get secret -n default
NAME                                     TYPE                             DATA   AGE
chu-awssm-secret                         Opaque                           2      8m15s
private-registry                         kubernetes.io/dockerconfigjson   1      7m14s
sc-key                                   Opaque                           1      5m27s

(Include any relevant logs/screenshots)

Linked Issue

issue

Upgrade Notices

N/A

Closes #46 (closed)