# Custom Types and Processors
By default, the operator syncs secret values as they are in Doppler to an [`Opaque` Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/) as Key / Value pairs.
In some cases, the secret name or value stored in Doppler is not the format required for your Kubernetes deployment.
For example, you might have Base64-encoded TLS data that you want to copy to a native Kubernetes TLS secret.
Processors provide a mechanism to achieve this.
Below is the Doppler Secret used in the Getting Started example with some modifications.
```yaml
apiVersion: secrets.doppler.com/v1alpha1
kind: DopplerSecret
metadata:
name: dopplersecret-test
namespace: doppler-operator-system
spec:
tokenSecret:
name: doppler-token-secret
This file has been truncated. show original
