-
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
kubectl <1.17 fails with error: type names don't match (Unknown, RawExtension) #10859
Comments
I am see this error too.
I couldn't find the
|
My suspicion, based on the error message, is that this may be caused by new annotations minikube adds to the KUBECONFIG file. It may be that your version of kubectl (v1.16.0) is too old to accept them. Here is the PR that added this feature to minikube 1.17.x: #10126 |
My kubectl version is
|
WORKAROUND:
|
This is why we include "minikube kubectl", to get a version that matches the cluster. |
I have a Mac OS system
to fix the issue use the following You may have to delete kubectl if it is > v17 and already exists
|
|
@JakeAtTurner Thank you! This works for me. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
We actually warn when the installed version of kubectl on the host doesn't match the version of kubernetes installed by minikube. Using |
Deleting config and delete/start minikube by re-installing cluster is not working. The solution is that you need to install compatible version of kubectl.exe to your installed kubernetes version.on your mini-kube. I have v1.24.0 kubernetes and I use v1.22.0 kubectl.exe . Now it is working successfully. |
Following worked for me for a similar issue. rm '/usr/local/bin/kubectl' |
I have Windows OS _> kubectl config view What to Do Now...? |
Steps to reproduce the issue:
1.install latest version of minikube
I Installed into Ubuntu 18.04.3 LTS
amd64 / x86_64
Binary download
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
sudo install minikube-linux-amd64 /usr/local/bin/minikube
run kubectl config view
get error :
kubectl config view
error: converting to : type names don't match (Unknown, RawExtension), and no conversion 'func (runtime.Unknown, runtime.RawExtension) error' registered.
Full output of failed command:
error: converting to : type names don't match (Unknown, RawExtension), and no conversion 'func (runtime.Unknown, runtime.RawExtension) error' registered.
Full output of
minikube start
command used, if not already included:minikube start
😄 minikube v1.18.1 on Ubuntu 18.04
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing docker container for "minikube" ...
🐳 Preparing Kubernetes v1.20.2 on Docker 20.10.3 ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v4
▪ Using image kubernetesui/dashboard:v2.1.0
▪ Using image kubernetesui/metrics-scraper:v1.0.4
🌟 Enabled addons: storage-provisioner, default-storageclass, dashboard
❗ /usr/local/bin/kubectl is version 1.16.0, which may have incompatibilites with Kubernetes 1.20.2.
▪ Want kubectl v1.20.2? Try 'minikube kubectl -- get pods -A'
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
Optional: Full output of
minikube logs
command:The text was updated successfully, but these errors were encountered: