<p>I have Google cloud composer running in 2 GCP projects. I have updated composer environment variable in both. One composer restarted fine within few minutes. I have problem in another &amp; it shows below error as shown in images.</p>
<p><strong>Update operation failed. Couldn't start composer-agent, a GKE job that updates kubernetes resources. Please check if your GKE cluster exists and is healthy.</strong></p>
<p><a href="https://i.stack.imgur.com/vMytz.png" rel="nofollow noreferrer">This is the error what I see when I enter the composer</a></p>
<p><a href="https://i.stack.imgur.com/JYTJP.png" rel="nofollow noreferrer">This is the environment overview</a></p>
<p><a href="https://i.stack.imgur.com/RMWSq.png" rel="nofollow noreferrer">GKE cluster notification</a></p>
<p><a href="https://i.stack.imgur.com/mDyes.png" rel="nofollow noreferrer">GKE pods overview</a></p>
<p>I am trying to find how to resolve the problem but I didn't find any satisfied answers. My colleagues are assuming firewall &amp; org policies issue but I haven't changed any.</p>
<p>Can some one let me know what caused this problem as the google composer is managed by google &amp; how to resolve this issue now?</p>

John
<p>Once the Cloud Composer is the managed resource and when the GKE which serves the environment for your composer is unhealthy you should try to contact Google Cloud Support. That GKE should work just fine and you do not need even know about its existence.</p>
<p>Also check whether you do not reacy any limits or quotas in your project.</p>
<p>When nothing helps recreation of Cloud Composer is always good idea.</p>
