Question
403 Response on doctl kubernetes cluster kubeconfig save
- Posted on October 17, 2023
- DigitalOcean Managed KubernetesCI/CD
Asked by 168557d4aa8f4a1ab2f7824af56ddd
We’ve been using Gitlab CI since forever and everything worked fine until this night. Started from this morning the doctl kubernetes cluster kubeconfig save command fails from the pipeline resultin in a 403 response.
The command follows the previous doctl auth init -t dop_v1_*** command which returns a Validating token... Ok response.
The exact response is; Error: GET [https://api.digitalocean.com/v2/kubernetes/clusters/[MASKED]/kubeconfig](https://api.digitalocean.com/v2/kubernetes/clusters/[MASKED]/kubeconfig): 403 (request "d83cadb5-3be2-44a3-ae77-e9921fd21cad") you do not have access for the attempted action
The exact same commands do work when executed locally.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Featured on Community
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Also it can be that your token access has expired, You need to go to DigitalOcean Web interface>API and recreate another token and register it doing doctl auth init --access-token <token>
This is resolved. The key needs write permissions since an update today!
This is resolved. The key needs write permissions since an update today!