<p>I am setting up a <code>kind</code> cluster</p>
<pre><code>Creating cluster &quot;kind&quot; ...
 ✓ Ensuring node image (kindest/node:v1.22.1) 🖼 
 ✓ Preparing nodes 📦 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
 ✓ Joining worker nodes 🚜 
 ✓ Waiting ≤ 5m0s for control-plane = Ready ⏳ 
 • Ready after 0s 💚
</code></pre>
<p>and then trying to install ECK operator as per <a href="https://www.elastic.co/guide/en/cloud-on-k8s/1.6/k8s-deploy-eck.html" rel="noreferrer">instructions</a> about version 1.6</p>
<pre><code>kubectl apply -f https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml
</code></pre>
<p>However the process fails, as if <code>kind</code> does not support CRDs...Is this the case?</p>
<pre><code>namespace/elastic-system created
serviceaccount/elastic-operator created
secret/elastic-webhook-server-cert created
configmap/elastic-operator created
clusterrole.rbac.authorization.k8s.io/elastic-operator created
clusterrole.rbac.authorization.k8s.io/elastic-operator-view created
clusterrole.rbac.authorization.k8s.io/elastic-operator-edit created
clusterrolebinding.rbac.authorization.k8s.io/elastic-operator created
service/elastic-webhook-server created
statefulset.apps/elastic-operator created
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;CustomResourceDefinition&quot; in version &quot;apiextensions.k8s.io/v1beta1&quot;
unable to recognize &quot;https://download.elastic.co/downloads/eck/1.6.0/all-in-one.yaml&quot;: no matches for kind &quot;ValidatingWebhookConfiguration&quot; in version &quot;admissionregistration.k8s.io/v1beta1&quot;
</code></pre>

pkaramol
<p>The problem you're seeing here isn't related to kind, instead it's the manifest you're trying to apply is using outdated API versions, which were removed in Kubernetes 1.22</p>
<p>Specifically the manifest is using the v1beta1 version of the customresourcedefinition object and validatingadmissionwebhook object</p>
<pre><code>apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
</code></pre>
<p>As noted in <a href="https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/" rel="noreferrer">this post</a> that was one of the versions removed when 1.22 went in.</p>
<p>There's a couple of fixes for this. Firstly you could get the manifest and just change the customresourcedefinitions to use the new API version <code>apiextensions.k8s.io/v1</code> and validatingadmissionwebhook to use <code>admissionregistration.k8s.io/v1</code>.</p>
<p>The other fix would be to use an older version of Kubernetes. if you use 1.21 or earler, that issue shouldn't occur, so something like <code> kind create cluster --image=kindest/node:v1.21.2</code> should work.</p>
