I received this email: kubernetes:authenticate_in_cluster permission enabled. Kubeconfigs downloaded after October 18, 2024 contain tokens with this permission. However, your current kubeconfig contains a token with different permissions. This can be due to one of the following:
-
- The kubeconfig was downloaded from the Control Panel UI before October 18, 2024
- You have replaced the token in your kubeconfig with a manually-generated one.
When I re-download the kubeconfig from the control panel, it is the same as the one currently installed, so I am confused.
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!
Hey there!
If you’re re-downloading the kubeconfig now and it’s the same as your current one, it’s possible that your token was already updated at some point after October 18, and you’re all set, the warning might just be a leftover notification.
If you want to be sure, you can:
-
Delete your local kubeconfig for that cluster (or move it as a backup),
-
Download a fresh copy from the control panel,
-
Test access using
kubectlto confirm it’s working.
If you’re still seeing unexpected behavior, I’d recommend opening a support ticket with DigitalOcean, they will be able to help out further:
- Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.