-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
kubeadm: pull kubernetes-anywhere per job #9117
Conversation
images/kubeadm/runner
Outdated
@@ -21,14 +21,6 @@ if [ ! -e test-infra ]; then | |||
git clone https://github.com/kubernetes/test-infra |
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.
should this be moved to --repo
as well eventually?
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 should be left up to the underlying runner in the base image, when using bootstrap.py we have a runner that does some things like that. that runner is also needed for EG the bazel cache.
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.
really we should just do away with this runner being the entrypoint and do any of:
- do things ahead of time, eg pre-installing tools in the image
- let bootstrap check things out
- let the testing script do things
instead of the runner / entrypoint.
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 need to look up what the base image is.
images/kubeadm/runner
Outdated
@@ -21,14 +21,6 @@ if [ ! -e test-infra ]; then | |||
git clone https://github.com/kubernetes/test-infra | |||
fi | |||
|
|||
if [ ! -e kubernetes-anywhere ]; then |
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.
we have -e
checks in the runner. i guess using --repo
for the jobs instead would pull every time?
probably OK for smaller repos.
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 doesn't really make sense, I don't think this check would be true under any circumstance
images/kubeadm/runner
Outdated
# immediately break e2e jobs, and we have control over upgrading/downgrading. | ||
git -C kubernetes-anywhere checkout a26f42c716028c4ba967b2d2f3de5ed50acc51da | ||
fi | ||
|
||
# This is required until https://github.com/kubernetes/kubernetes-anywhere/issues/332 |
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've re-opened this issue as it still exists.
images/kubeadm/runner
Outdated
# immediately break e2e jobs, and we have control over upgrading/downgrading. | ||
git -C kubernetes-anywhere checkout a26f42c716028c4ba967b2d2f3de5ed50acc51da | ||
fi | ||
|
||
# This is required until https://github.com/kubernetes/kubernetes-anywhere/issues/332 | ||
# is implemented. | ||
if [ ! -e kubernetes-anywhere/phase1/gce/account.json ]; then |
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.
@BenTheElder you've mentioned that --repo
would pull in $PWD/../kubernetes-anywhere
do i need to adjust the paths in this last part of the file to be ../kubernetes-anywhere/
?
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 also saw the discussion about not having a custom image.
i'm not exactly sure why the ln -s
action is here and not in the kubernetes-anywhere tree, but is it possible to move the ./test-infra/jenkins/bootstrap.py
call in the job?
this can go in a separate PR too, i guess.
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.
So when the init scripts hand off to the testing code the current directory will be a checkout of the first --repo flag, which is typically the repo under test. Additional repos will be adjacent in ./../$OTHER_REPO.
I'm not sure why we do anything in this image. Ideally we'd use the underlying runner in the base image only and not do anything at runtime in this image.
/lgtm |
d52fa12
to
9901d56
Compare
@BenTheElder the kubeadm runner now looks like the one for gcloud: i still don't understand what the base image is, but for the kubeadm image i'm seeing that it installs terraform, so i'm not exactly sure how the kubeadm image can be removed: possibly this has to happen in a separate PR. |
le bump. 👀 |
images/kubeadm/runner
Outdated
@@ -1,5 +1,5 @@ | |||
#!/usr/bin/env bash | |||
# Copyright 2017 The Kubernetes Authors. | |||
# Copyright 2018 The Kubernetes Authors. |
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.
we should drop this runner entirely, we can use the entrypoint from the base image
Sorry I got behind on PR reviews, going through the backlog today.
We don't need to remove this image, but we should drop the runner. The base images for this go like: |
@@ -9,6 +9,7 @@ periodics: | |||
- image: gcr.io/k8s-testimages/e2e-kubeadm:v20180730-c8036c3a7 | |||
args: | |||
- --repo=k8s.io/kubernetes=master | |||
- --repo=k8s.io/kubernetes-anywhere=kubeadm-e2e |
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.
skimming through this PR I don't see us doing this for other k-a jobs (the presubmits?) we should find them and do this for all k-a jobs
9901d56
to
b7798f9
Compare
b7798f9
to
30cd445
Compare
30cd445
to
97ed199
Compare
updated:
|
@neolit123: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
kubernetes-anywhere (k-a) now has a specific branch for use with e2e tests and it is no longer needed to bake a k-a commit SHA into the kubeadm image. The following is used to pull the `kubeadm-e2e` branch of k-a: `--repo=k8s.io/kubernetes-anywhere=kubeadm-e2e` This removes a step where after fixing a k-a bug, the test-infra kubeadm image has to be updated. Also removes the kubeadm runner as it is no longer needed.
97ed199
to
370260f
Compare
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.
/lgtm
/hold
we should bump the images after this, will do that
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, neolit123, timothysc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks for tackling this! :-) |
thanks a lot. |
alright let's merge this, I'll send out an image bump PR to go with it |
@neolit123: Updated the
In response to this:
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 think this might be the first indication that something is not right about the new k-a setup:
perhaps it's not cloning in the correct folder. https://k8s-testgrid.appspot.com/sig-cluster-lifecycle-all#gce-kubeadm-upgrade-1.10-1.11 waiting on some of the other tests to start too. |
I don't see a .config in that repo? https://github.com/kubernetes/kubernetes-anywhere/tree/kubeadm-e2e |
i don't have enough details. edit: investigating. |
not sure, but |
i think i found a problem in the logs:
so it's checked out in i think i need to update the value of test-infra/kubetest/anywhere.go Line 160 in b5f298b
as |
kubernetes-anywhere (k-a) now has a specific branch for use with
e2e tests and it is no longer needed to bake a k-a commit SHA into
the kubeadm image.
ref:
kubernetes-retired/kubernetes-anywhere#555
kubernetes/kubernetes#66338
The following is used to pull the
kubeadm-e2e
branch of k-a:--repo=k8s.io/kubernetes-anywhere=kubeadm-e2e
This removes a step where after fixing a k-a bug, the test-infra
kubeadm image has to be updated.
/area jobs
/assign @BenTheElder
/cc @timothysc
/cc @mohammedzee1000