-
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
Minikube v0.25 & k8 v1.8.0 Dashboard Deployment Not Compatible #2521
Comments
We should really version the addons according to the kube version, but we don't do that today. The addons are actually versioned with minikube instead. The best workaround would be to disable the dashboard addon with |
Practically, would that mean adding a set of addons for each kube version under
I see. Thanks for the suggestion. |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Please provide the following details:
Environment:
Minikube version (use
minikube version
):minikube version: v0.25.0
cat ~/.minikube/machines/minikube/config.json | grep DriverName
):cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):What happened:
K8s dashboard does not start when using v1.8.0 K8s because of 08f4677
I believe in v1.8.0
apiVersion
has to beapps/v1beta2
in order for deployments to work.What you expected to happen:
The dashboard to start.
How to reproduce it (as minimally and precisely as possible):
minikube start --kubernetes-version=v1.8.0
Output of
minikube logs
(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: