<p>after cloning repo (tag v1.14.0)to local machine; i have modified <code>cmd/kube-apiserver/app/server.go</code> file; i hvae added one line of new code which is custome log entry
upon K8s code compilation i found docker images tar ball in <code>_output/release-images/amd64/</code>  and i used <code>docker load -i _output/release-images/amd64/kube-apiserver.tar
</code>
it adds a newly built apiserver docker image but, rather than overwriting to tag  it creates a new tag <code>v1.14.0-dirty</code> </p>

<p><a href="https://i.stack.imgur.com/2IiMI.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/2IiMI.png" alt="enter image description here"></a></p>

<p>now my question is <strong>how and why K8s is adding <code>dirty</code> suffix to image tag?</strong>
Now when i do kubeam init it will still deploy original image with <code>v1.14.0</code> tag and will not deploy newly built image which has <code>v1.14.0-dirty</code> tag</p>

<p><strong>how do i launch K8s with newly built docker images?</strong> </p>

ankit patel
<p>A quick and dirty solution would be to add another command: </p>

<pre><code>docker tag k8s.gcr.io/kube-apiserver:v1.14.0-dirty k8s.gcr.io/kube-apiserver:v1.14.0
</code></pre>

<p>That should create the correct tag for the image. </p>

<p>The <code>dirty</code> tag could be applied during the tar build stage as the builder detects that the git repository state is <em>dirty</em>.</p>
