The GitOps Helm Chart currently only supports adding the agentSecret directly in the values.yaml file. We'd like the ability to define an existing K8S secret here instead of putting the secret in the values.yaml file as plain text.

Our organization uses External Secrets Operator (ESO) to fetch secrets from AWS Secrets Manager and create Kubernetes secrets automatically. We need the ability to reference these existing secrets in the Helm chart rather than embedding secret values directly in values.yaml.