-
Notifications
You must be signed in to change notification settings - Fork 817
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
Update minikube dev tooling #1906
Conversation
Needed to update minikube to Kubernetes 1.17.x and I figured I would also go through the minikube dev experience and update it. This includes: * Switch to default to the Docker driver, since everyone should have Docker installed. * Removing the Windows hacks, because they were awful and I feel bad I even wrote them in the first place. * Migrate tooling to use new minikube functionality * Update minikube commands to up to date release conformity. * Updated the documentation Work on googleforgames#1824
Build Succeeded 👏 Build Id: b30af332-2458-48cb-b732-a454237dd365 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
@@ -653,20 +638,22 @@ Since Minikube runs locally, there are some targets that need to be used instead | |||
|
|||
#### `make minikube-test-cluster` | |||
Switches to an "agones" profile, and starts a kubernetes cluster |
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 see that additional command which changes profile was removed. Was it redundant?
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 now powered by the -p
argument in minikube start
- which also creates the profile. minikube profile foo
will not create the profile if it doesn't exist.
export DOCKER_CERT_PATH=$$(echo $$DOCKER_CERT_PATH | $(win_to_wsl_path)) | ||
|
||
# minikube shell mount for certificates | ||
minikube_cert_mount = $(cert_path):$(cert_path) |
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 think this one should stay there
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 the previous Windows support was super hacky, brittle and I expect it doesn't work anymore.
We were rewriting windows path to linux paths in make files. If we decide to continue supporting it, it needs a whole new rewrite. So I've removed it for now. If we need to add new os specific tooling, then lets revisit then. Right now, between OSX and Linux, it's all the same.
MINIKUBE_DOCKER_ENV ?= eval $$($(MINIKUBE) docker-env) | ||
|
||
# minikube shell mount for certificates | ||
minikube_cert_mount := ~/.minikube:$(HOME)/.minikube |
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 one also might be needed and be different for different OSs. WDYT?
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.
For OSX and Linux it's the same.
It may be the same for minikube under WSL, but it requires testing. But I figure we can revisit if we decide it's possible to support windows without hackery.
MINIKUBE_DRIVER ?= docker | ||
|
||
# minikube shell mount for certificates | ||
minikube_cert_mount := ~/.minikube:$(HOME)/.minikube |
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.
It seems that Windows would not have this folder. Am I missing something? I can test on my other PC.
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 why I changed the README to:
https://github.com/googleforgames/agones/pull/1906/files#diff-4b71ec736aee936feb417e5193e800a1014a8e2df2a5b5b92fd78fbd3d781dbdR122
The Minikube setup on Windows has not been tested. Pull Requests would be appreciated!
I expect it will all fall apart. Last time I looked at this (many years ago now), kubectl on WSL wouldn't work with minikube because the minikube config referenced certs hosted at C:\
which doesn't work for Linux.
I expect the entire Windows dev environment setup would need a review anyway. (do we even have anyone developing on windows?)
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.
Got an idea. That would be a leftover from this PR.
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.
Since we have the git history to go back and look at if we need it, I'm not convinced it's necessary to leave this in, given that we don't actually know what the correct path is for windows+minikube dev (or if we even want to support it).
This feels to me like leaving in commented out code in the current source repo.
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.
+1 to not leaving stuff in that is "dead code" in the hope that we will fix it later. It's better to clean it up and we can always look at repo history if necessary to pull it back in.
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.
In which case, I will merge this, and we can revisit Windows at a later date 👍
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.
Left small comments regarding minikube_cert_mount
which might need to be OS-specific.
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. Please address @aLekSer's comments before merging.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey 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 |
@roberthbailey do you want to tiebreak on this PR? |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 2106ebf5-b282-41fc-b5c4-46559c717234 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
Needed to update minikube to Kubernetes 1.17.x and I figured I would also go through the minikube dev experience and update it.
This includes:
Which issue(s) this PR fixes:
Work on #1824
Special notes for your reviewer:
N/A