No way to determine CNI images ahead of time

[thomasjm]

What Happened?

I'd like to be able to programmatically determine the images that will be pulled by a Minikube cluster for different CNI settings. For example, if you enable Calico via --cni=calico, my version of Minikube will currently pull these images:

docker.io/calico/cni:v3.27.3
docker.io/calico/kube-controllers:v3.27.3
docker.io/calico/node:v3.27.3

But these images may change from version to version. AFAICT, they are baked into the Minikube binary and there's no way to determine what they are without examining the code.

Minikube doesn't even print information about the images if you run minikube start with the highest verbosity.

This feature request is for a way to determine these images with the CLI, akin to how minikube addons images ADDON_NAME works. An explicit command would be nice, or perhaps it could print them when you run minikube start --dry-run --cni=calico -v=something.

Attach the log file

-

Operating System

Ubuntu

Driver

Docker

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale