Skip to content

Add architecture to the binaries and images in the cache #9593

Closed
@afbjorklund

Description

@afbjorklund

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

Metadata

Metadata

Assignees

Labels

co/generic-driverkind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions