<p>I created a Kubernetes cluster with the following CLI command:
<code>
gcloud container clusters create some-cluster --tags=some-tag --network=some-network
</code></p>

<p>I would now like to:</p>

<ol>
<li>Disable the <code>--tags</code> option, so that new nodes/VMs are created <em>without</em> the tag <code>some-tag</code>. (Optional: Remove the tag from existing machines, which should be possible through <code>gcloud compute instances remove-tags</code>.)</li>
<li>Disable the <code>--network</code> flag, returning the cluster to the default GCP network.</li>
</ol>

<p>Are either of these operations possible, or will I have to re-create the cluster?</p>

<p>For context, I was using the node tags and networking rules to route outgoing network traffic through a single GCE instance serving as a NAT gateway. I now want to turn this routing off.</p>

Andy Barron
<p>Currently, its not possible to update cluster network and remove tags for existing cluster using the gcloud command. I have verified this information using the gcloud container clusters update command <a href="https://cloud.google.com/sdk/gcloud/reference/container/clusters/update" rel="noreferrer">documentation</a>. Additionally, <a href="https://cloud.google.com/sdk/gcloud/reference/alpha/container/clusters/update" rel="noreferrer">alpha</a> and <a href="https://cloud.google.com/sdk/gcloud/reference/beta/container/clusters/update" rel="noreferrer">beta</a> command don't provide this feature yet. API doc also provides information related to different configuration which can be changed. </p>

<p>As a workaround, I was able to remove one of the tags using the rolling update feature within the instance group setting:</p>

<blockquote>
  <ol>
  <li>Go to instance template of some-cluster -> select the template </li>
  <li>Click (copy from the top of instance template)-> Remove the tag -> creates a new template</li>
  <li>Select the some-cluster Instance Group-> click on rolling update -> change the instance template to the one you created -> update</li>
  </ol>
</blockquote>

<p>If you change the network in step-2, I was not able to select the instance template with the new network in step-3. Changing the tag alone won’t solve your purpose, it's better to create a new cluster.</p>

<p>If you are interested to update tags and network using the gcloud command, I suggest creating a feature request (FR) in <a href="http://%20https://issuetracker.google.com/" rel="noreferrer">Public Issue tracker</a>. </p>
