v2.7.8 - error messages - cluster.x-k8s.io

[smirnov-mi]

Rancher Server Setup single docker installation, v.2.5.x updated many times, last update : v2.7.7 to 2.7.8

Information about the Cluster rancher-provisioned cluster 1.26.8-rancher1 on Hetzner VMs

User Information admin local login in rancher, since OpenLDAP stopped working in 2.7.1

Describe the bug docker logs of the rancher container:

W1006 05:55:39.749726 48 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment W1006 05:55:55.768430 48 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet W1006 05:57:11.373174 48 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine W1006 05:57:35.235644 48 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster W1006 05:59:33.698876 48 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck

To Reproduce install Rancher single container, update 2.7.7 to 2.7.8

Result

Expected Result no error messages

[smirnov-mi]

might be related to https://github.com/rancher/rancher/issues/42999

[smirnov-mi]

a part of https://github.com/rancher/rancher/issues/43075

[chfrank-cgn]

I'm observing the same error message in the Rancher pod logs on a fresh 2.7.9 install on RKE1 1.24:

W1123 12:26:42.459049      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster
W1123 12:27:08.292747      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck
W1123 12:27:11.440043      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment
W1123 12:27:38.271223      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine
W1123 12:29:14.659582      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet

[Prafulrakhade]

After upgrading rancher version from v2.6.3 to v2.7.9, getting error in the rancher pod

W1124 11:42:15.684397      33 warnings.go:80] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W1124 11:45:21.274961      33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine
W1124 11:46:05.968093      33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster
W1124 11:47:00.971701      33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet
W1124 11:50:23.400226      33 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment

[smirnov-mi]

it looks like it's fixed in the 2.8.0 release:

https://github.com/rancher/rancher/blob/v2.8.0/pkg/crds/provisioningv2/crds.go

[jitbasemartin]

Always present with v2.8.0

W0110 22:34:36.409921      33 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster

[Oats87]

I believe this is happening as we use a "dynamic" client that is registering controllers, but as it's dynamic it's trying to grab any usable version i.e. even deprecated ones.

More investigation into this is necessary to ensure we're not actually trying to use v1alpha3 or v1alpha4 anywhere ...

[rmweir]

We do pass GVK to dynamic client that we key off resource fields like so https://github.com/rancher/rancher/blame/v2.7.8/pkg/controllers/capr/machinenodelookup/controller.go#L111.

We use discovery client to set the servers GVK's. These are most of what is returned when requesting schemas. The UI uses schemas and may be watching against these old versions which would throw the warning.

@smirnov-mi can you share the output of <rancher-url>/v1/schemas?

I tried to repro with an upgrade from 2.7.7 to 2.7.8 but we are already using the updated resource by that point. Whoever works on this may need to provision a cluster before capi-crds were updated https://github.com/rancher/rancher/commit/d3b5469238e965e54306f74d0e98a47b780cbe80#diff-f8e60a8a2fed04ae80021a577117695e3764832c9db9e31fa724ded8c03533a2 in order to get resources on older versions.

[smirnov-mi]

clean installation v2.8.0 -> 2.8.1 -> 2.8.2 - the issue is still present. https://github.com/rancher/rancher/issues/44755

[smirnov-mi]

the output of <rancher-url>/v1/schemas?

it only contains "betav1", no "alpha"s. :-(

57k lines of code, can be found here: https://github.com/smirnov-mi/k8s/blob/main/Rancher/various/2.8.0-2.8.2-x-k8s.io.schemas

[CTPEKO3AT0P]

In my case (fresh install 2.8.3) i have no single "betav1", in the https://rancher.orange-ftgroup.ru/v1/schemas but 827 "v1alpha"s. :-(

[chfrank-cgn]

On a fresh installation of Rancher 2.8.3 the issue is still present:

W0428 11:10:18.481280      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine
W0428 11:12:15.895399      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet
W0428 11:13:04.434826      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment
W0428 11:13:21.684418      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster
W0428 11:14:54.082643      32 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck

[ahazelwood]

Still happening with Rancher 2.8.4.

W0531 13:55:11.363577      55 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster
W0531 13:56:08.947709      55 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck
W0531 13:57:05.965458      55 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet
W0531 13:57:35.005853      55 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine
W0531 13:57:47.156313      55 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineDeployment is deprecated; use cluster.x-k8s.io/v1beta1 MachineDeployment

Additional version information

Component | Version
Rancher | v2.8.4
Dashboard | v2.8.4
Helm | v2.16.8-rancher2
Machine | v0.15.0-rancher112

[smirnov-mi]

still see it on a fresh 2.8.5 installation (single container setup)

W0619 11:15:08.881022 44 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck W0619 11:15:38.953843 44 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet

[epiHATR]

Getting the same issues on fresh install of rancher via docker Rancher: 2.8.0