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
Build release tars using bazel #39898
Conversation
386b1bc
to
fff44e7
Compare
Jenkins kops AWS e2e failed for commit 386b1bcf1ae7959924a34401f63d92ef5a122e94. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins verification failed for commit 386b1bcf1ae7959924a34401f63d92ef5a122e94. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
fff44e7
to
c53bc50
Compare
Jenkins GCE etcd3 e2e failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins GCI GCE e2e failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins unit/integration failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins CRI GCE Node e2e failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins GCE e2e failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins Kubemark GCE e2e failed for commit fff44e7fd6da44c85369da83fe24b12b17485af6. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
making a few changes/fixes, sorry for the noise. I think this should be working now. |
c53bc50
to
b9e060a
Compare
I lied. But maybe now. |
Jenkins GCE Node e2e failed for commit 1ecca07. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
tags = ["automanaged"], | ||
) | ||
|
||
# TODO(#3579): This is a temporary hack. It gathers up the yaml, |
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.
How temporary?
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.
I copied the comment from here. I'm still not sure if it's necessary or not.
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.
Ah, "temporary"
|
||
genrule( | ||
name = "dummy", | ||
outs = [".dummy"], |
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.
😕
Overall this looks really spiffy. Have you reached out to the bazel people about the docker rule updates? |
I'm not too happy the build speeds, but we can optimize later. It's still significantly faster than |
cmd = "touch $@", | ||
) | ||
|
||
# Some of the startup scripts fail if there isn't an addons/ directory in the server tarball. |
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.
TODOD: delete this
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.
yeah, this part makes me sad. I'm not sure how many places assume server/addons/
exists, but that can hopefully be addressed in a follow-up.
This is so beautiful i cried |
/lgtm |
Jenkins GCI GKE smoke e2e failed for commit 1ecca07. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins GKE smoke e2e failed for commit 1ecca07. Full PR test history. cc @ixdy The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@k8s-bot gke e2e test this |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
What this PR does / why we need it: builds equivalents of the various kubernetes release tarballs, solely using bazel.
For example, you can now do
Special notes for your reviewer: this is currently dependent on ixdy/bazel@3b29803, which I have yet to turn into a pull request, since I'm still trying to figure out if this is the best approach.
Basically, the issue comes up with the way we generate the various server docker image tarfiles and load them on nodes:
md5sum
the binary being encapsulated (e.g. kube-proxy) and save that to$binary.docker_tag
in the server tarballgcr.io/google_containers/kube-proxy:$MD5SUM
)docker save
this image, which embeds the full tag in the$binary.tar
file.docker load
these tarballs, which are loaded with the tag that we'd created at build time. the nodes then use the$binary.docker_tag
file to find the right image.With the current bazel
docker_build
rule, the tag isn't saved in the docker image tar, so the node is unable to find the image afterdocker load
ing it.My changes to the rule save the tag in the docker image tar, though I don't know if there are subtle issues with it. (Maybe we want to only tag when
--stamp
is given?)Also, the docker images produced by bazel have the timestamp set to the unix epoch, which is not great for debugging. Might be another thing to change with a
--stamp
.Long story short, we probably need to follow up with bazel folks on the best way to solve this problem.
Release note: