-
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
Sign minikube binaries for macOS #5792
Comments
This issue is currently waiting on an official signing protocol from Kubernetes. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Related issues, all blocked on signing infra: |
#sig-release issue: kubernetes/release#839 |
we still like to do this ! if anyone can help , help wanted ! |
@prezha I wonder if u would like to take on this issue to start the conversation and add signing for minikube binaries? |
@medyagh an interesting one - i accept the challenge! |
I think we have already given up on the deb and rpm, the current apt and yum repositories are deprecated and the new ones are not taking new projects (SIGs) So signing for Windows Store has higher priority Arguably re-adding the snap to Ubuntu after that... |
re: releases - repos, package managers & signing (#5792, #3110, #4716, kubernetes/release#839, etc.) - a brief update on this:
i've tested it with opensuse tumbleweed, debian 11, centos 8, and it would be great if others would also be interested in testing these repos with their favourite apt/yum package manager and report back if it's working for them or not (something like "full os: result" [w/ error details if any] would be ok) if it works (for most, at least) and would be useful, we might promote it to "production" and publish the gpg key (https://keys.openpgp.org/vks/v1/by-fingerprint/61BCC110C8DFD072E2326DC92591E036E40127C3) on our website as well thanks! |
@prezha is there anything new on this? |
@medyagh sorry for my late reply on this topic i've explored it a bit more and the findings are collated in a doc open for comments: TL;DR: signing minikube binaries for macOS and Windows requires funding ($99/year and a wide range of ~$80-$700+/year respectively), and for Linux distros, we currently have an operational YUM and APT repos. we can discuss options at our next office hours meeting |
Under what URL could I find those? The ones I found are unsigned |
hey @septatrix, there wasn't a big interest in these linux repos, so they haven't been kept up to date, and also the cert expired in the meantime i've now refreshed the cert and added & signed all the release (ie, without beta and alpha) versions from minikube v1.24.0 - v1.26.1 (current atm), so you can try please follow the steps above for your linux distro/package manager and share if it's working for you now this is what apt reports now:
|
This would make it play better with Catalina.
There are some issues here in that the sig-release folks keep a tight reign on the Kubernetes certificate.
The text was updated successfully, but these errors were encountered: