When saving Kubernetes config from doctl with an existing API token, another token is created . Is this normal?
Let’s say I want to programmatically save the Kubeconfig of my Kubernetes cluster using doctl :
doctl -t "$DIGITALOCEAN_ACCESS_TOKEN" \ 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?