VKR 1.35.0 Error - Could not resolve KR/OSImage Missing compatible KR/OSImage for the cluster
search cancel

VKR 1.35.0 Error - Could not resolve KR/OSImage Missing compatible KR/OSImage for the cluster

book

Article ID: 436733

calendar_today

Updated On:

Products

Tanzu Kubernetes Runtime VMware vSphere Kubernetes Service

Issue/Introduction

Unable to create a new VKS (vSphere Kubernetes Service) cluster on VKR (vSphere Kubernetes Release) v1.35.0.

Cannot create new node-pools for an existing VKS cluster on VKR v1.35.0.

Unable to upgrade from VKR v1.34 to VKR v1.35.0.

 

While connected to the Supervisor cluster context, the following symptoms are observed:

  • Creating a new cluster on VKR v1.35.0 returns an error message similar to the below:
    Error from server (Forbidden): error when creating <new cluster>: admission webhook "tkr-resolver-cluster.webhook.tanzu.vmware.com" denied the request: Could not resolve KR/OSImage
    Missing compatible KR/OSImage for the cluster
    Control Plane, filters: {k8sVersionPrefix: v1.35.0, osImageSelector: os-name=<OS>}
    MachineDeployment <node-pool-name>, filters: {k8sVersionPrefix: v1.35.0, osImageSelector: os-name=<OS>}

     

  • Adding a new node-pool to an existing VKS cluster already on VKR v1.35.0 returns a similar KR/OSImage error to the above.

  • Upgrading an existing VKS cluster on v1.34.X to v1.35.0 fails similarly.

  • The status of VKR v1.35.0 shows Ready False but the VKS supervisor service version is v3.6.0 or higher:
    kubectl get kr v1.35.0---vmware.2-vkr.4
    
    NAME                       VERSION                  READY   COMPATIBLE
    v1.35.0---vmware.2-vkr.4   v1.35.0+vmware.2-vkr.4   False   True

     

  • Describing KR v1.35.0 shows that it is Deactivated:
    kubectl describe kr v1.35.0---vmware.2-vkr.4
    
    status:
      conditions:
      - lastTransitionTime: "YYYY-MM-DDTHH:MM:SSZ"
        message: deactivated
        reason: Deactivated
        severity: Warning
        status: "False"
        type: Ready

Environment

vSphere Supervisor v1.30 or higher

VKR v1.35.0

VKS 3.6.0 or higher

Cause

VKR v1.35.0 has been deactivated and can no longer be used to create or upgrade clusters or provision new nodepools.

Only Create operations regarding new VKS clusters on v1.35.0, new node-pools on VKR v1.35.0 or upgrades to VKR v1.35.0 are prevented.

Resolution

Upgrade the affected VKS cluster to VKR v1.35.2.

Existing nodes running on VKR v1.35.0 are not affected.

VKS clusters on v1.34.X will only be able to upgrade to VKR v1.35.2

See Understanding TKR Deactivated Status for details

Additional Information

VKR v1.35.2 Release Notes