I'm working on setting up a development environment for my company based on minikube, and draft seems like a great fit -- except that the cycle time from saving a file to having it running on the cluster is longer than it'd like. Of the ~15 seconds it takes to update the service, about 8 seconds is pushing the image (which is a 19MB image).

For now, i've rolled my own upgrade path that does:

eval "$(minikube docker-env)"
docker build -t my-app .

kubectl delete pod -l app=my-app --grace-period=0 --force

and have the image tag in my helm package be "latest". This is much faster, but loses all the other nice benefits of draft.

Would you be open to adding an option to use a flow like this (probably with a helm upgrade or even a kubectl set image) when minikube is detected, rather than the default push-to-registry flow? I'm happy to help with implementation, but wanted to check whether this is something you'd consider merging. Pointers to where to look to implement this change would also be much appreciated.