Closed
Description
When supporting remote clusters of a different architecture, we need to add the arch in addition to the OS:
~/.minikube/cache/linux/v1.19.3
├── kubeadm
├── kubectl
└── kubelet
Simplest would be to add it after the OS, but we could support both in order to preserve existing user caches ?
~/.minikube/cache/linux
├── amd64
│ └── v1.19.3
│ ├── kubeadm
│ ├── kubectl
│ └── kubelet
└── arm64
└── v1.19.3
├── kubeadm
├── kubectl
└── kubelet
For instance when running an amd64
host, towards a arm64
machine. Either local hardware or cloud instance.
-
Raspberry Pi
-
AWS Graviton
Same thing for the images, if not using the preload (the preloaded-tarball files already include the arch, though)
~/.minikube/cache/images
├── gcr.io
│ └── k8s-minikube
│ └── storage-provisioner_v3
├── k8s.gcr.io
│ ├── coredns_1.7.0
│ ├── etcd_3.4.13-0
│ ├── kube-apiserver_v1.19.2
│ ├── kube-controller-manager_v1.19.2
│ ├── kube-proxy_v1.19.2
│ ├── kube-scheduler_v1.19.2
│ └── pause_3.2
└── kubernetesui
├── dashboard_v2.0.3
└── metrics-scraper_v1.0.4
~/.minikube/cache/images/amd64
~/.minikube/cache/images/arm64