This message was deleted.
# kubernetes
s
This message was deleted.
f
In my case, I've found that encrypting the doppler token with sealed secret really neat, as it allows to keep everything in git Curious to get your opinions on this
s
secrets in git 😬
f
https://github.com/bitnami-labs/sealed-secrets should prevent the secret to leak 😅 as it is encrypted So the Doppler token would be encrypted, meaning if the secret is deleted by mistake, or it needs to be recreated at some point, there is no need to reran manual commands to generate the secrets
s
yep, still going to make everyone working in appsec have their spidey sense tingle
f
What would you do instead to use Doppler on Kubernetes? ^^ (In a production/secure fashion)
or CI + the doppler cli if you don't want to do TF, shouldn't ever need to store the service token
generate it when you need it and rotate often 🤷
f
I see, it seems nice 👌 So it never keeps the token “hardcoded” somewhere A downside would be to let the CI or TF access the cluster, so it is not “gitops” friendly