-
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
Make it possible to use custom GCS with environment variables #2368
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Can one of the admins verify this patch? |
CLA signed |
@afbjorklund you can already pass in a file or url to kubernetes version for localkube --kubernetes-version=https://... |
@r2d4 : that was one of the first things that I tried, but it doesn't seem to work - just got errors.
So using the pre-populated cache was a workaround, which worked OK (for v1.8.0, not v1.8.4) |
The previous version (0.23) just said:
|
@afbjorklund what string did you try passing as a flag to get that error? |
@dlorenc : Something like |
I think that this was a regression in 0.23.0 but fixed at HEAD. Especially since we use the flag in this way for integration tests |
Am running 0.24.1, maybe should have said that. |
Hmm, git says c20ebde was included in 0.24.0 already... Now when I retry same thing with minikube 0.24.1, it does say: |
What's the status here? Can this be closed? |
@dlorenc : I guess that if you wanted to run e.g. 1.8.7 or 1.9.2 that you would "have" to use something like this since the default list of localkubes is still hardcoded to 1.8.0 and 1.9.0. But using an URL seems to be working (as a workaround), even if it spews some "semver" errors when trying to parse the URL. Seems to be choking on the first path of the url/path ?
But I suppose we could patch it downstream, so you can just close it if you like. |
It would be nice if this could be merged, since the syntax is much nicer and having validation is good... MINIKUBE_LOCALKUBE_GCS=https://storage.googleapis.com/minikube/k8s_releases.json |
Add environment variables, for alternative locations: $MINIKUBE_LOCALKUBE_GCS https://storage.googleapis.com/minikube/k8s_releases.json $MINIKUBE_LOCALKUBE_URL https://storage.googleapis.com/minikube/k8sReleases/ Since minikube is no longer making localkube releases. Signed-off-by: Anders F Björklund <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: afbjorklund Assign the PR to them by writing 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 |
Is this still needed? Localkube is on the way out. Please reopen if you think it should be included still. |
It was used for previous kubernetes releases, but like you say it is not useful without |
I know that "localkube" is deprecated, and that there are no official versions of localkube since v1.8.0:
#2134
But since the list of releases is hardcoded, I can't make any custom localkube builds (of 1.8.x) either:
#2156
Plan to move to "kubeadm" eventually (1.9+), but am not ready to do it for kubernetes version 1.8
And besides, using docker-machine and localkube still works fine - unless it is hardcoded/blocked...