Has the authentication part in the kubernetes secret to be repeated over and over?

[Ergamon]

I have set up Infisical and the secrets operator. In general it works fine, but it feels strange for me to have the authentication in every secret.

apiVersion: secrets.infisical.com/v1alpha1
kind: InfisicalSecret
metadata:
  name: sample
  namespace: test

spec:
  hostAPI: https://infisical.domain.com/api
  resyncInterval: 10
  authentication:
    kubernetesAuth:
      autoCreateServiceAccountToken: true
      identityId: xxx
      secretsScope:
        envSlug: "dev"
        projectSlug: "proj"
        secretsPath: "/"
      serviceAccountRef:
        name: default
        namespace: test

  managedKubeSecretReferences:
    - secretName: managed-secret
      secretNamespace: test
      creationPolicy: "Orphan"
      template:
        includeAllSecrets: true

Maybe it is our setup, but we have a cluster for every project and every environment.
So far I have only found a way to have the hostAPI at the central config.

Unless I miss something, every secret will look the same in these lines.

so I would wish I could write something like this:

apiVersion: secrets.infisical.com/v1alpha1
kind: InfisicalSecret
metadata:
  name: sample
  namespace: test

spec:
  authentication:
    kubernetesAuth:
        secretsPath: "/"

  managedKubeSecretReferences:
    - secretName: managed-secret
      secretNamespace: test
      creationPolicy: "Orphan"
      template:
        includeAllSecrets: true

We have dozens of microservices and having these fixed values over and over feels not right for me or do I just set things up wrong?

[varonix0]

Hi @Ergamon, thank you for reaching out. We have a planned initiative for an improved version of the operator API, which will modularize things such as authentication for reusability. Thank you for raising this point, we'll keep you updated on when we release the improved operator API!