<p>I'm trying to make a development environment using minikube.<br>
I'm using <code>minikube image load</code> to upload local images to the cluster.<br>
here is an example deployment:</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: sso
spec:
  selector:
    matchLabels:
      app: mm
  template:
    metadata:
      labels:
        app: mm
        name: sso
    spec:
      containers:
        - name: sso
          image: sso-service
          imagePullPolicy: Never
          resources:
            limits:
              memory: &quot;128Mi&quot;
              cpu: &quot;500m&quot;
          ports:
            - containerPort: 3000
      imagePullSecrets:
        - name: pull-secret
</code></pre>
<p>The first time I run <code>minikube image load &quot;sso-service&quot;</code> the deployment restarts, but after that, loading a new image doesn't cause a rollout with the new image.<br>
I also tried running <code>kubectl rollout restart</code>, did not help.<br>
Is there any way to force the deployment to perform a rollout with the new image?</p>

GideonMax
<p>Managed to solve this myself.
I made a script that would first generate a random number and use it as the image's tag, it would then use <code>kubectl set image</code> to update the image.</p>
<pre class="lang-default prettyprint-override"><code>$tag = $(Get-Random)
echo &quot;building image&quot;
docker build --build-arg NPM_TOKEN=$(cat .token) -t &quot;sso-service:$tag&quot; .
echo &quot;loading image&quot;
minikube image load &quot;sso-service:$tag&quot; --daemon=true
kubectl set image deployment/sso sso=&quot;sso-service:$tag&quot;
</code></pre>
