<p>This is a Google Cloud specific problem.
I returned from vacation and noticed I can no longer manage workloads or cluster due to this error: &quot;Missing edit permissions on account&quot;</p>
<p><a href="https://i.stack.imgur.com/A1cxM.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/A1cxM.png" alt="enter image description here" /></a></p>
<p><a href="https://i.stack.imgur.com/dA7ed.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/dA7ed.png" alt="enter image description here" /></a></p>
<p>I am a sole person with access to this account (owner role) and yet I see this issue.
The troubleshooting <a href="https://cloud.google.com/kubernetes-engine/docs/troubleshooting?&amp;_ga=2.209122386.-1512594765.1552850111#gke_service_account_deleted" rel="nofollow noreferrer">guide</a> suggests checking system service account role, looks like it's set up correctly (why would it not if I haven't edited it):
<a href="https://i.stack.imgur.com/qmLet.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qmLet.png" alt="enter image description here" /></a>
If it's not set up correctly it suggests turning off/on the Kubernetes API on GCP, but when you press on &quot;disable&quot; there's a scary-looking prompt that your Kubernetes resources are going to be deleted, so obviously I can't do that.</p>
<p>Upon trying to connect to it I get</p>
<pre><code>gcloud container clusters get-credentials cluster-1 --zone us-west1-b --project PROJECT_ID
Fetching cluster endpoint and auth data.
WARNING: cluster cluster-1 is not running. The kubernetes API may not be available.
</code></pre>
<p>In the logs I found a record (the last one) that is 4 days old:</p>
<blockquote>
<p>&quot;Readiness probe failed: Get <a href="http://10.20.0.5:44135/readiness" rel="nofollow noreferrer">http://10.20.0.5:44135/readiness</a>: net/http: request canceled (Client.Timeout exceeded while awaiting headers)&quot;</p>
</blockquote>
<p>Anyone here has any ideas?
Thanks in advance.</p>

TheRusskiy
<p>The issue is solved,
I had to upgrade node versions in the pool.
What a misleading error message.
Hopefully, this helps someone.</p>
