<p>I am using GKE cluster with master version <code>1.15.9-gke.24</code> and linkerd2 as proxy for my <code>gRPC</code> services. </p>

<p>From my cluster I saw calico node vertical autoscaler pod is in <code>CrashLoopBackOff</code> state. From log I see following</p>

<pre><code>$ kubectl logs -f calico-node-vertical-autoscaler-7767597775-rd68v -n kube-system
I0503 10:36:55.586271       1 autoscaler.go:46] Scaling namespace: kube-system, target: daemonset/calico-node
E0503 10:36:55.720025       1 autoscaler.go:49] unknown target kind: Tap
</code></pre>

<p>According to <a href="https://github.com/linkerd/linkerd2/issues/3388#issuecomment-608169755" rel="nofollow noreferrer">this</a> I need to update from <code>k8s.gcr.io/cpvpa-amd64:v0.8.1</code> to <code>k8s.gcr.io/cpvpa-amd64:v0.8.2</code>. I edited the deployment and replace the version. But it seems gke reset the image version to <code>v0.8.1</code>. How can I modify the version without uprading cluster?</p>

<p>Additional information:</p>

<pre><code>    $ linkerd version
    Client version: stable-2.7.1
    Server version: stable-2.7.1
</code></pre>

hoque
<blockquote>
  <p>I edited the deployment and replace the version. But it seems gke reset the image version to v0.8.1. How can I modify the version without uprading cluster?</p>
</blockquote>

<p>When you tried to edit the manifest to upgrade cpvpa image to 0.8.2 it got to 0.8.1 since GKE is a managed cluster, which is an intended behaviour. </p>

<ul>
<li><p>Any changes made to a <code>kube-system</code> object will be automatically reverted, this happens because the addon-manager will perform the necessary actions to preserve it state.</p></li>
<li><p>Direct manipulation to these addons through apiserver is discouraged because addon-manager will bring them back to the original state.  </p></li>
</ul>

<p><strong>Upgrading the cluster Version once the release of 0.8.2 is available on the  <a href="https://cloud.google.com/kubernetes-engine/docs/release-notes" rel="nofollow noreferrer">GKE Release Notes</a> page is the only recommended way to get it.</strong></p>

<ul>
<li>As a workaround I suggest you try setting the <code>priorityClass</code> and <code>priorityClassName</code> configurations in Linkerd configuration as mentioned in the <a href="https://github.com/linkerd/linkerd2/issues/3388#issuecomment-553486915" rel="nofollow noreferrer">Github Issue</a> as the solution while 0.8.2 is not available.</li>
</ul>

<p>If you need further help let me know in the comments!</p>
