Synthetics Private Location - helm chart example using configSecret

[jmanuelortizn]

Describe what happened: Using: argocd to deploy datadog synthetic pvt location with the following values:

values:
  configSecret: private-location-worker-config

Secret private-location-worker-config is a valid secret Opaque

Describe what you expected: configFile should be setup using the secret private-location-worker-config

Instead an error is shown on logs saying:

2023-12-19 01:54:16 [warn]:     No configuration file found, using parameters from command line arguments.
2023-12-19 01:54:16 [error]:    Configuration is invalid:
- Public key to encrypt results ("publicKey" field) must be set
- Access key ("accessKey" field) must be set
- Secret access key ("secretAccessKey" field) must be set
- Private key to decrypt test configs ("privateKey" field) must be set

Steps to reproduce the issue: Deploy argocd app Note: datadog secret should be deployed in datadog namespace

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: dd-private-location
  namespace: argocd
spec:
  project: default
  source:
    chart: synthetics-private-location
    repoURL: https://helm.datadoghq.com
    targetRevision  : "0.15.*"
    helm:
      values: |
        configSecret: private-location-worker-config
  destination:
    server: "https://kubernetes.default.svc"
    namespace: datadog
  syncPolicy:
    managedNamespaceMetadata:
      labels:
        pod-security.kubernetes.io/enforce: baseline
    syncOptions:
      - CreateNamespace=true
    automated:
      selfHeal: true
      prune: true

Additional environment details (Operating System, Cloud provider, etc):

• On premise
• argocd

[nidhiben]

Curious, on how did you configure the secret. I am facing this issue when I am trying to create the secret using SecretProviderClass custom resource and storing the worker configuration AWS secret manager and accessing it via IRSA.

[jmanuelortizn]

@nidhiben

I am using sealed secrets, sealed secret create the opaque secret and I am referencing that opaque secret from helm values

apiVersion: bitnami.com/v1alpha1
kind: SealedSecret

[a-Name]

Hi, did you eventually manage to get your private location running ? Thanks for the feedback!