dashboard endpoint removal

Stopped workingMay 1, 2026Subscribe to Linode API (Akamai Cloud)Share

Akamai Cloud decommissioned the LKE-hosted Kubernetes Dashboard on May 1, 2026. Requests to the GET /{id}/lke/clusters/{id}/dashboard endpoint fail since that date. The dashboard is no longer available for existing LKE clusters and cannot be deployed to new clusters.

Calls it hits

GET /{id}/lke/clusters/{id}/dashboard

What to use instead of these calls

Remove calls to this endpoint. There is no direct replacement because Akamai no longer hosts a dashboard for LKE clusters, so you must install a Kubernetes dashboard or another cluster UI yourself if one is needed.

No replacement: Akamai no longer hosts a dashboard for LKE clusters.

In Linode API (Akamai Cloud)'s words

Akamai Cloud decommissioned the LKE-hosted Kubernetes Dashboard. This change occurred in May 2026. The Kubernetes Dashboard is no longer available for existing LKE clusters and can't deploy to new clusters.

Linode API (Akamai Cloud), Announcement

Facts

API: Linode API (Akamai Cloud) api.linode.com
Kind: Endpoint removal
Takes effect: May 1, 2026
Calls after that day: Fail
Source: Announcement
Last updated: November 6, 2026
Verified: November 6, 2026, against Linode API (Akamai Cloud)'s own pages

Questions

When does this change take effect?

Calls to GET /{id}/lke/clusters/{id}/dashboard on Linode API (Akamai Cloud) stopped working on May 1, 2026.

What happens to calls after May 1, 2026?

They have failed since May 1, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub