-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add architecture to the binaries and images in the cache #9593
Comments
Also, this code needs to be parameterized: src, err := download.Binary(name, cfg.KubernetesVersion, "linux", runtime.GOARCH)
if err != nil {
return errors.Wrapf(err, "downloading %s", name)
} if _, err := download.Binary(bin, version, "linux", runtime.GOARCH); err != nil {
return errors.Wrapf(err, "caching binary %s", bin)
} func archTag(hasTag bool) string {
if runtime.GOARCH == "amd64" && !hasTag {
return ":"
}
return "-" + runtime.GOARCH + ":"
} var defaultPlatform = v1.Platform{
Architecture: runtime.GOARCH,
OS: "linux",
} Basically split host arch and cluster (node?) arch. Using runtime.GOARCH is a good default, but it needs to be possible to override. It is still OK to hardcode the OS (for now...), since Kubernetes only runs on Linux. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Ok, this has become more of an issue recently, since if someone accidentally runs an amd64 minikube binary on an arm machine, it corrupts their cache. Let's fix this one and for all. |
When supporting remote clusters of a different architecture, we need to add the arch in addition to the OS:
Simplest would be to add it after the OS, but we could support both in order to preserve existing user caches ?
For instance when running an
amd64
host, towards aarm64
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)
The text was updated successfully, but these errors were encountered: