Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

tl;dr: Is it safe to have a doctl access token in a secret inside kubernetes? What is a good alternative?
I have my domain with mrdomain, I can’t change the dns to use digital ocean’s because to keep using the email from mrdomain they need to manage the domain. I want to use the spaces with CDN and i’m using lets encrypt to generate SSL certs once every 2 months.
I’ve written a container to be run on a CronJob that:
It works fine, but I need to run doctl compute certificate create, doctl compute cdn update and doctl compute certificate delete. Those 3 commands need a token with write permission.
If anyone get access to this token they will have unlimited access to wreak havoc on our account.
So my question is, is it safe to keep this under a kubernetes secret? Is there a better option?
c21c0b00bb284130a0d0cd3b7bdab4
IsaacMvd
Leon Junior
hashembarret@gmail.com
JetForMe
24608ead89f046a8abab394f968f2c
Philipp Mayerhofer
enews
Brian Magnosi
jairunet
Nikolas Jakson