Upgrading from 2.2.2 to 2.2.3 error: xit status 1, unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls

I have a few clusters, 2 on AWS launched using RKS and one importer from DigitalOcean Managed K8s (DOKS).

After I upgraded all the clusters are showing as provisioning with error:

 	Exit status 1, unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error unable to recognize "management-statefile_path_redacted": Get https://localhost:443/k8s/clusters/c-f7wxh/api?timeout=32s: remote error: tls: internal error 

However I am still able to access all the clusters, upgrade workloads and do everything as normal.

2 Likes