3

I receive the following error when i try to download calico.yaml files for the pod network

unable to recognize "calico.yaml": no matches for kind "Deployment" in version "apps/v1beta1" unable to recognize "calico.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"

here is the full output when i run "kubectl apply -f calico.yaml"

'configmap/calico-config created service/calico-typha created poddisruptionbudget.policy/calico-typha created serviceaccount/calico-node created customresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org created customresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org created unable to recognize "calico.yaml": no matches for kind "Deployment" in version "apps/v1beta1" unable to recognize "calico.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"'

Community
  • 1
  • 1
parrot_boy
  • 43
  • 1
  • 4

3 Answers3

5

If you are using the latest version Kubernetes, API versions of few resources have been changed. Try converting calico.yaml to use updated API by using kubectl convert command to update API versions

Eduardo Baitello
  • 10,469
  • 7
  • 46
  • 74
Praveen
  • 81
  • 3
  • I tried using ' Kubectl convert ' and received Error saying that 'kubectl convert is DEPRECATED and will be removed in a future version. In order to convert, kubectl apply the object to the cluster, then kubectl get at the desired version. unable to decode "calico.yaml": no kind "CustomResourceDefinition" is registered for version – parrot_boy Nov 02 '19 at 21:50
  • 1
    I used the current up to date Calico.yaml and applied it and it fixed the Issue. Download yaml files for your pod network kubectl apply -f calico.yaml curl https://docs.projectcalico.org/v3.10/manifests/calico.yaml -O – parrot_boy Nov 04 '19 at 00:29
3

Confiming, getting "latest" file via command:

wget:docs.projectcalico.org/v3.10/manifests/calico.yaml

resolved my issue.

Was following pluralsight course and it was referencing yaml file from "https://docs.projectcalico.org/v3.3/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.7/calico.yaml"

Which was resulting in:

unable to recognize "calico.yaml": no matches for kind "Deployment" in version "apps/v1beta1"
unable to recognize "calico.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1"
Rider_BY
  • 1,129
  • 1
  • 13
  • 31
0

I used the current up to date Calico.yaml and applied it and it fixed the Issue. Download yaml files for your pod network kubectl apply -f calico.yaml curl docs.projectcalico.org/v3.10/manifests/calico.yaml -O

parrot_boy
  • 43
  • 1
  • 4