-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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 a KUBERNETES_NODE_* section to build kubelet/kube-proxy for windows #38919
Conversation
Jenkins CRI GCE Node e2e failed for commit f5a3781. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE Node e2e failed for commit f5a3781. Full PR test history. The magic incantation to run this job again is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a quick fix indeed and might work, but we should do this properly (in time for v1.6, not a cherrypick candidate) and remove kubelet and the proxy from the server targets and refactor the build/release framework to take the node targets into account
linux/arm64 | ||
linux/s390x | ||
windows/amd64 | ||
windows/386 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need 386 here? Are you actually using it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably not, though apparently there are still windows/386
users out there. x-ref #28632
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed. Windows 2016 is required for Windows containers, and it's not build for 386 afaik know.
@k8s-bot node e2e test this |
@k8s-bot cri node e2e test this |
@k8s-bot build this |
@k8s-bot build this |
@k8s-bot build this |
Jenkins GCE e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE etcd3 e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GKE smoke e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GCE e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins Kubemark GCE e2e failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
Jenkins Cross Build failed for commit d6cbf130fea348848105481518bd5047e3cbe19f. Full PR test history. The magic incantation to run this job again is |
@k8s-bot build this |
@ixdy @luxas This appears to work correctly and packages a new node tarball. @luxas I don't want to remove them from the server tarball (yet) because that would likely break numerous release scripts. Eventually (probably not even in 1.6, but maybe 1.7) we can remove them from the server tarball... Please take another look. Thanks! |
LGTM Yes, I didn't mean it should be done now, but maybe for v1.7 we should remove kubelet and the proxy from the server targets @ixdy can apply the label if he also thinks it's ok |
Ping to @ixdy for approval on this. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works! Thanks @brendandburns.
yes, sorry, I will take a look today. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
basically LG. you'll probably need to update https://github.com/kubernetes/release/blob/master/lib/releaselib.sh#L480-L491 too.
cp "${node_bins[@]/#/${LOCAL_OUTPUT_BINPATH}/${platform}/}" \ | ||
"${release_stage}/node/bin/" | ||
|
||
# TODO: Docker images here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
open an issue for this?
/lgtm I'd like to see an issue filed to possibly remove these from the server tarball, so we reduce duplication. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Removing label |
@pires @ixdy
Addresses #38785 (I hope)