# Doppler K8 Operator basic auth

**URL:** <https://community.doppler.com/t/doppler-k8-operator-basic-auth/1532>\
**Category:** Need Help\
**Created:** [May 21, 2024, 3:15pm UTC](https://community.doppler.com/t/doppler-k8-operator-basic-auth/1532 "2024-05-21T15:15:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![steflsd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/steflsd/32/1061_2.png) [@steflsd](https://community.doppler.com/u/steflsd)\
**Post date:** [May 21, 2024, 3:15pm UTC](https://community.doppler.com/t/doppler-k8-operator-basic-auth/1532/1 "2024-05-21T15:15:07Z")

</div>

Hi,

We’re using the Doppler Kubernetes operator to sync secrets from Doppler to our k8 cluster. This works well using the envFrom for example and passing all the env variables through to a pod for example.

I wanted to configure a K8 ingress route which is protected by basic auth. Essentially the secret for this is

```auto
apiVersion: v1
data:
  username: encryptedkey=
kind: Secret
type: Opaque

```

Im trying to replicate creating this secret with dopplersecrets. The closest i’ve been able to come is

```auto
apiVersion: v1
data:
  DOPPLER_CONFIG: ZXV5
  DOPPLER_ENVIRONMENT: ZXV5
  DOPPLER_PROJECT: DFJKSmcS
  username: encryptedkey=
kind: Secret
type: Opaque

```

This is achieved with something like

```auto
apiVersion: secrets.doppler.com/v1alpha1
kind: DopplerSecret
metadata:
  name: doppler-secrets-app # DopplerSecret Name
  namespace: doppler-operator-system
spec:
  tokenSecret: # Kubernetes service token secret (namespace defaults to doppler-operator-system)
    name: doppler-token-secret
  secrets:
    - APP_PASSWORD
  project: project
  config: env
  managedSecret: # Kubernetes managed secret (will be created if does not exist)
    name: app-ingress-nginx-auth-test
    namespace: observability # Should match the namespace of deployments that will use the secret
  processors:
    APP_PASSWORD:
      type: plain
      asName: username

```

Im not sure if i can exclude the DOPPLER\_ENVIRONMENT / CONFIG / PROJECT. It would also be useful if there was a processor that could concatenate two value, as basic auth is some combination of username:password.

Is there a better way to do this to get a single secret and create a k8 opague secret?

Thanks!

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [May 21, 2024, 8:30pm UTC](https://community.doppler.com/t/doppler-k8-operator-basic-auth/1532/2 "2024-05-21T20:30:50Z")

</div>

Hi @steflsd,

Welcome to the Doppler Community!

Unfortunately, there isn’t currently a way of preventing the `DOPPLER_` secrets from getting synced as well.

In terms of concatenating two values – you can do that using [Secret References](https://docs.doppler.com/docs/secrets#referencing-secrets). For example, you could create a new secret called `BASIC_AUTH_SECRET` and then set the value to `${USERNAME}:${PASSWORD}` and then sync this secret over to Kubernetes. Would that work for you?

Regards,  
-Joel