How to efficiently manage authentication in Kubernetes secrets without repetition?

[ghost]

Hi team,

I’m using Infisical to manage secrets in a Kubernetes environment. I noticed that the authentication part in the Kubernetes secrets seems to be repeated multiple times.

Is there a recommended way to avoid this repetition?
Can we centralize the authentication info, or is repetition required for each secret?
Are there best practices or examples for managing this efficiently with Infisical?

Thanks in advance for any guidance!

[Om-singh-ui]

You don’t necessarily need to repeat the authentication part for every Kubernetes secret. A common approach is to use a single central Secret or ConfigMap that stores the shared authentication information, then reference it in multiple places using Kubernetes features like envFrom or secretKeyRef.

For example:

apiVersion: v1
kind: Secret
metadata:
  name: infisical-auth
type: Opaque
stringData:
  token: "<YOUR_INFISICAL_TOKEN>"

Then in your pod/deployment:

env:
  - name: INFISICAL_TOKEN
    valueFrom:
      secretKeyRef:
        name: infisical-auth
        key: token

This way, you only store the auth info once and can inject it wherever needed. Infisical’s Kubernetes integration supports this pattern, so you can keep your deployments DRY (Don’t Repeat Yourself) and maintainable.

hope that it helps!