Answers: <p>The answer is appearently that there's a bug in Minikube 0.26. Downgrading the Minikube installation is solving it.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-07-12T09:00:48.007Z
Answers: I have restarted the minikube and then finally works for me.
Answers: Rahul Sinha
Answers: CC BY-SA 4.0
Answers: 2018-05-13T11:21:57.957Z
Answers: 2018-05-13T11:21:57.957Z
Answers: Black Magic
Body: <p>I ran minikube with: </p>
  
  <pre><code>minikube start --vm-driver=kvm2 --kubernetes-version=v1.8.0
  </code></pre>
  
  <p>status:</p>
  
  <pre><code>minikube: Running
  cluster: Running
  kubectl: Correctly Configured: pointing to minikube-vm at 192.168.39.93
  </code></pre>
  
  <p>However, running <code>kubectl get all</code> returns this error:</p>
  
  <pre><code>error: the server doesn't have a resource type "cronjobs"
  </code></pre>
  
  <p>Anyone have any idea what could be the reason for this?</p>
  
Comments: CC BY-SA 4.0
Comments: 2018-05-08T20:16:02.507Z
Comments: What does `kubectl get ns` return?
Comments: 030
Comments: CC BY-SA 4.0
Comments: 2018-05-08T20:54:10.383Z
Comments: What kubectl version?
Comments: 030
Tags: <kubernetes><minikube>
Title: Kubectl: the server doesn't have a resource type "cronjobs"
UserDisplayName: Black Magic
ThreadText: # Kubectl: the server doesn't have a resource type "cronjobs"
  
  (Asked by: username_0 on 2018-05-08)
  
  I ran minikube with:
  
  ```
  minikube start --vm-driver=kvm2 --kubernetes-version=v1.8.0
  
  ```
  
  status:
  
  ```
  minikube: Running
  cluster: Running
  kubectl: Correctly Configured: pointing to minikube-vm at 192.168.39.93
  
  ```
  
  However, running `kubectl get all` returns this error:
  
  ```
  error: the server doesn't have a resource type "cronjobs"
  
  ```
  
  Anyone have any idea what could be the reason for this?
  
  **Tags:** kubernetes, minikube
  
  > **Comments:**
  > **username_1**: What does `kubectl get ns` return?  
  > **username_1**: What kubectl version?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-05-13. Score: 0 | Accepted answer
  
  The answer is appearently that there's a bug in Minikube 0.26. Downgrading the Minikube installation is solving it.
  
  > **Comments:**
  > **username_2**: I have restarted the minikube and then finally works for me.  
  
  ---
  
  