<p>I have installed a 3 nodes cluster with <strong>K3S</strong>. Nodes are correctly detected by <code>kubectl</code> and I'm able to deploy images.</p>
<pre><code>$ k3s kubectl get nodes
NAME                   STATUS   ROLES                       AGE     VERSION
master                 Ready    control-plane,etcd,master   4h31m   v1.22.2+k3s1
worker-01              Ready    &lt;none&gt;                      3h59m   v1.22.2+k3s1
worker-02              Ready    &lt;none&gt;                      4h3m    v1.22.2+k3s1
</code></pre>
<p>I've also installed <strong>Rancher</strong> latest version (<code>2.6.0)</code> via docker-compose:</p>
<pre><code>version: '2'
services:
  rancher:
    image: rancher/rancher:latest
    restart: always
    ports:
    - &quot;8080:80/tcp&quot;
    - &quot;4443:443/tcp&quot;
    volumes:
    - &quot;rancher-data:/var/lib/rancher&quot;
    privileged: true
volumes:
  rancher-data:
</code></pre>
<p>The dashboard is reachable from every node and I've imported an existing cluster, running the following command:</p>
<pre><code>curl --insecure -sfL https://192.168.1.100:4443/v3/import/66txfzmv4fnw6bqj99lpmdt6jlx4rpwblzhx96wvljc8gczphcn2c2_c-m-nz826pgl.yaml | kubectl apply -f -
</code></pre>
<p>The cluster apears as <strong>Active</strong> but with 0 nodes and with message:</p>
<pre><code>[Pending] waiting for full cluster configuration
</code></pre>
<p>The full yaml status is here:</p>
<pre><code>apiVersion: provisioning.cattle.io/v1
kind: Cluster
metadata:
  annotations:
    field.cattle.io/creatorId: user-5bk6w
  creationTimestamp: &quot;2021-10-05T10:06:35Z&quot;
  finalizers:
  - wrangler.cattle.io/provisioning-cluster-remove
  generation: 1
  managedFields:
  - apiVersion: provisioning.cattle.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:&quot;wrangler.cattle.io/provisioning-cluster-remove&quot;: {}
      f:spec: {}
      f:status:
        .: {}
        f:clientSecretName: {}
        f:clusterName: {}
        f:conditions: {}
        f:observedGeneration: {}
        f:ready: {}
    manager: rancher
    operation: Update
    time: &quot;2021-10-05T10:08:30Z&quot;
  name: ofb
  namespace: fleet-default
  resourceVersion: &quot;73357&quot;
  uid: 1d03f05e-77b7-4361-947d-2ef5b50928f5
spec: {}
status:
  clientSecretName: ofb-kubeconfig
  clusterName: c-m-nz826pgl
  conditions:
  - lastUpdateTime: &quot;2021-10-05T10:08:30Z&quot;
    status: &quot;False&quot;
    type: Reconciling
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;False&quot;
    type: Stalled
  - lastUpdateTime: &quot;2021-10-05T14:08:52Z&quot;
    status: &quot;True&quot;
    type: Created
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: RKECluster
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: BackingNamespaceCreated
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: DefaultProjectCreated
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: SystemProjectCreated
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: InitialRolesPopulated
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: CreatorMadeOwner
  - lastUpdateTime: &quot;2021-10-05T10:08:15Z&quot;
    status: &quot;True&quot;
    type: Pending
  - lastUpdateTime: &quot;2021-10-05T10:08:15Z&quot;
    message: waiting for full cluster configuration
    reason: Pending
    status: &quot;True&quot;
    type: Provisioned
  - lastUpdateTime: &quot;2021-10-05T14:08:52Z&quot;
    message: Waiting for API to be available
    status: &quot;True&quot;
    type: Waiting
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: NoDiskPressure
  - lastUpdateTime: &quot;2021-10-05T10:06:35Z&quot;
    status: &quot;True&quot;
    type: NoMemoryPressure
  - lastUpdateTime: &quot;2021-10-05T10:06:39Z&quot;
    status: &quot;False&quot;
    type: Connected
  - lastUpdateTime: &quot;2021-10-05T14:04:52Z&quot;
    status: &quot;True&quot;
    type: Ready
  observedGeneration: 1
  ready: true
</code></pre>
<p>Cluster agent shows no particular issue:</p>
<pre><code>$ kubectl -n cattle-system logs -l app=cattle-cluster-agent
time=&quot;2021-10-05T13:54:30Z&quot; level=info msg=&quot;Connecting to wss://192.168.1.100:4443/v3/connect with token starting with 66txfzmv4fnw6bqj99lpmdt6jlx&quot;
time=&quot;2021-10-05T13:54:30Z&quot; level=info msg=&quot;Connecting to proxy&quot; url=&quot;wss://192.168.1.100:4443/v3/connect&quot;
</code></pre>
<p>Is there something I need to do to make the cluster fully running ? I've tried to downgrade the Rancher version to <code>2.5.0</code> but I got the same issue.</p>

<p>I believe this is an incompatibility with Kubernetes v1.22.</p>
<p>Having encountered the same issue with Rancher v2.6.0 when importing a new v1.22.2 cluster (running on IBM Cloud VPC infrastructure), I tailed the logs of the Docker container running Rancher and observed:</p>
<pre><code>2021/10/20 14:40:31 [INFO] Starting cluster controllers for c-m-cs78tnxc
E1020 14:40:31.346373      33 reflector.go:139] pkg/mod/github.com/rancher/client-go@v0.21.0-rancher.1/tools/cache/reflector.go:168: Failed to watch *v1beta1.Ingress: failed to list *v1beta1.Ingress: the server could not find the requested resource (get ingresses.meta.k8s.io)
</code></pre>
<p><a href="https://kubernetes.io/blog/2021/07/26/update-with-ingress-nginx/" rel="nofollow noreferrer">Kubernetes v1.22 updates NGINX-Ingress to v1.x</a>, which appears to be the cause, and there is an <a href="https://github.com/rancher/rancher/issues/33312" rel="nofollow noreferrer">open issue on the Rancher GitHub</a> to update it for compatibility with Kubernetes v1.22.</p>
<p>In the meantime, after recreating the new cluster using Kubernetes v1.21.5 on the same infrastructure, I was able to import it into Rancher successfully.</p>
