Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow kops jobs on CLI to use a custom Kubernetes build somehow #1454

Closed
zmerlynn opened this issue Dec 28, 2016 · 1 comment
Closed

Allow kops jobs on CLI to use a custom Kubernetes build somehow #1454

zmerlynn opened this issue Dec 28, 2016 · 1 comment
Assignees
@zmerlynn

Comments

@zmerlynn
Copy link
Member

This is a minor inconvenience.. you can easily run the job with E2E_UP=false; E2E_DOWN=false on an existing cluster (which you can bring up using a custom k8s build), but that doesn't help for e.g. e2e test development (because we'll still download kube binaries for the tests in dockerized-e2e-runner.sh. I think there's a solution here involving JENKINS_USE_EXISTING_BINARIES, but it may need a little more streamlining.
@zmerlynn zmerlynn self-assigned this Dec 28, 2016
@fejta
Copy link
Contributor

fejta commented Aug 14, 2017

We can now use kubetest --extract to solve this

@fejta fejta closed this as completed Aug 14, 2017
ostromart pushed a commit to ostromart/test-infra that referenced this issue Jul 26, 2019
@howardjohn @istio-testing
Switch circleci->prow required for cloudfoundry (kubernetes#1454)
7fe67df
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zmerlynn zmerlynn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fejta @zmerlynn