Extensions/v1beta1 depreciated in kubernetes 1.16

Rancher 2.x
1

Trying to figure out why my kubernetes 1.16 cluster cannot be imported into Rancher 2.2.8. My cluster is running on ubuntu 18.04 on hyper-v.

The yaml generated by rancher to import an existing cluster still references extensions/v1beta1 for kind: Deployment and for kind: DaemonSet

After changing apiVersion: extensions/v1beta1 to app/v1 for Deployment and DaemonSet, it imported ok. It’s currently in a waiting state (waiting for API). The message in Rancher is:

This cluster is currently Waiting ; areas that interact directly with it will not be available until the API is ready.

Waiting for API to be available

Any idea on what I can do to help this along? I realize that the link I posted above may actually be telling me what to do…but I do not understand. :confused:

Thank you.

2

All necessary changes to make 1.16 work will be in the next release, 1.16 is marked experimental in 2.3.0 (see https://github.com/rancher/rancher/issues/23206) and full support can be tracked in https://github.com/rancher/rancher/issues/22965.

For generic troubleshooting steps for imported clusters, see https://rancher.com/docs/rancher/v2.x/en/troubleshooting/imported-clusters/.