When saving Kubernetes config from doctl with an existing API token, another token is created . Is this normal?

October 29, 2019 115 views
DigitalOcean Managed Kubernetes DigitalOcean API and CLI (doctl)

Let’s say I want to programmatically save the Kubeconfig of my Kubernetes cluster using doctl :

      kubernetes cluster kubeconfig save "$CLUSTER_NAME"

I have at my disposal an Access token. However doing this creates a new API Key on my account, which I don’t understand the reason. Since I am providing a API token why should I create a new one? This may result in creating an excessive number of tokens.

Is this normal? Can we force doctl to use the provided API token throughout the full process?


Be the first one to answer this question.