minikube image load does not replaces minikube cache add

[ekneg54]

What Happened?

if I run minikube image load -p myprofile $(minikube image ls -p myprofile | grep -v '<none>') after provisioning my workloads the cache stays empty if I run minikube cache list.
Additionally after resetting the cluster with minikube delete -p myprofile && minikube start -p myprofile and deploy the same workloads again I notice heavy traffic on my internet connection.

In contrast if I use minikube cache add -p myprofile instead of minikube image load -p myprofile everything works as expected and I do not notice any heavy internet connection anymore.

Sadly the minikube cache add feature is deprecated. Please do not remove this feature before replacing it with a clear alternative.

Attach the log file

Operating System

Ubuntu

Driver

Docker

[Ritikaa96]

Hi, there is no log file attached. it will be helpful in referencing the issue.

[Ritikaa96]

/kind support

[Ritikaa96]

/triage needs-information

[afbjorklund]

Sadly the minikube cache add feature is deprecated. Please do not remove this feature before replacing it with a clear alternative.

The minikube cache is not really deprecated, that e8945f2 is a misunderstanding from some previous work.

• The new load command still uses the cache directory #10744

In theory it might be replaced by a --cache option to the load command, but that is not the default since it is intended to load local files or images...

• Document minikube image semantics about locations #12270