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.

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

Closed
jashandeep-sohi opened this issue Feb 7, 2018 · 6 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@jashandeep-sohi
Copy link

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

  • OS (e.g. from /etc/os-release):
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
ID_LIKE=archlinux
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName):
"kvm2"
  • ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
        "Boot2DockerURL": "file:///home/jsohi/.minikube/cache/iso/minikube-v0.25.1.iso",
        "ISO": "/home/jsohi/.minikube/machines/minikube/boot2docker.iso",
  • Install tools:
  • K8s Version:
$ cat ~/.minikube/profiles/minikube/config.json | jq '.KubernetesConfig.KubernetesVersion'
"v1.8.0"

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 be apps/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):

==== START logs for container kube-addon-manager of pod kube-system/kube-addon-manager-minikube ====                                                                                 
INFO: == Kubernetes addon manager started at 2018-02-07T19:28:37+0000 with ADDON_CHECK_INTERVAL_SEC=60 ==                                                                            
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply                                                                    
namespace "kube-system" configured                                                                                                                                                   
INFO: == Successfully started /opt/namespace.yaml in namespace  at 2018-02-07T19:28:38+0000                                                                                          
INFO: == Default service account in the kube-system namespace has token default-token-9gggx ==                                                                                       
find: /etc/kubernetes/admission-controls: No such file or directory                                                                                                                  
INFO: == Entering periodical apply loop at 2018-02-07T19:28:38+0000 ==                                                                                                               
INFO: Leader is minikube                                                                                                                                                             
configmap "kube-dns" created                                                                                                                                                         
pod "storage-provisioner" created                                                                                                                                                    
INFO: == Kubernetes addon ensure completed at 2018-02-07T19:28:38+0000 ==                                                                                                            
INFO: == Reconciling with deprecated label ==                                                                                                                                        
error: no objects passed to apply                                                                              
INFO: == Reconciling with addon-manager label ==                                                                                                                                     
service "kubernetes-dashboard" created                                                                                                                                               
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/dashboard-dp.yaml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" i$
 registered for version "apps/v1"                                                                                                                                                    
deployment "kube-dns" created                                                                                                                                          
service "kube-dns" created                                                                                                      
storageclass "standard" created                                                            
INFO: == Kubernetes addon reconcile completed at 2018-02-07T19:28:39+0000 ==                                     
INFO: Leader is minikube                                                                                                                                                             
INFO: == Kubernetes addon ensure completed at 2018-02-07T19:29:39+0000 ==             
INFO: == Reconciling with deprecated label ==                                                                
error: no objects passed to apply                                                                                                                                                    
INFO: == Reconciling with addon-manager label ==                                                                                                     
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/dashboard-dp.yaml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" i$
 registered for version "apps/v1"                                                                                
INFO: == Kubernetes addon reconcile completed at 2018-02-07T19:29:39+0000 ==                                     
INFO: Leader is minikube                                                                                          
INFO: == Kubernetes addon ensure completed at 2018-02-07T19:30:39+0000 ==                                                                            
INFO: == Reconciling with deprecated label ==                                                                                   
error: no objects passed to apply                                                                                       
INFO: == Reconciling with addon-manager label ==                                               
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/dashboard-dp.yaml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" i$
 registered for version "apps/v1"                                                                     
INFO: == Kubernetes addon reconcile completed at 2018-02-07T19:30:39+0000 ==                                                                                                         
INFO: Leader is minikube                                                                                                                                                             
INFO: == Kubernetes addon ensure completed at 2018-02-07T19:31:39+0000 ==                                      
INFO: == Reconciling with deprecated label ==                                                                                                                                        
error: no objects passed to apply                                                                                                                                                    
INFO: == Reconciling with addon-manager label ==                                                                                                                                     
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/dashboard-dp.yaml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" i$
 registered for version "apps/v1"                                                                                                                    
INFO: == Kubernetes addon reconcile completed at 2018-02-07T19:31:39+0000 ==                                                    
INFO: Leader is minikube                                                                   
INFO: == Kubernetes addon ensure completed at 2018-02-07T19:32:39+0000 ==                                        
INFO: == Reconciling with deprecated label ==                                                                                                                                        
error: no objects passed to apply
INFO: == Reconciling with addon-manager label ==
Error from server (BadRequest): error when creating "/etc/kubernetes/addons/dashboard-dp.yaml": Deployment in version "v1" cannot be handled as a Deployment: no kind "Deployment" is
 registered for version "apps/v1"
INFO: == Kubernetes addon reconcile completed at 2018-02-07T19:32:39+0000 ==
==== END logs for container kube-addon-manager of pod kube-system/kube-addon-manager-minikube ====                                              

Anything else do we need to know:

@r2d4
Copy link
Contributor

r2d4 commented Feb 7, 2018

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 minikube addons disable dashboard and run the yaml yourself by putting your own YAML in ~/.minikube/addons.

@jashandeep-sohi
Copy link
Author

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.

Practically, would that mean adding a set of addons for each kube version under deploy/addons. That might be too much. I'm not familiar w/ how addon-manager works, but some sort of templating would certainly help. And that immediately makes me think of Helm. Maybe use Helm charts to manage addons?

The best workaround would be to disable the dashboard addon with minikube addons disable dashboard and run the yaml yourself by putting your own YAML in ~/.minikube/addons.

I see. Thanks for the suggestion.

@jar349
Copy link

jar349 commented Feb 12, 2018

minikube addons disable dashboard
followed by:
kubectl get svc -n kube-system
still shows the kubernetes-dashboard service.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 3, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 3, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants