CloudBees CI managed controller operations fail on Kubernetes 1.33 due to unrecognized field "emulationMajor"

Issue

When provisioning, restarting, or deprovisioning a managed controller, the following error is seen in the operations center logs for that managed controller:

ERROR: Failed to provision controller: <controller-name>: null:An error has occurred.
...
Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "emulationMajor" (class io.fabric8.kubernetes.client.VersionInfo) ...▼

ERROR: Failed to restart controller: <controller-name>: null:An error has occurred.
...
Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "emulationMajor" ...▼

This issue is caused by running CloudBees CI on an unsupported version of Kubernetes, where the Kubernetes client library does not yet recognize the new emulationMajor field added in Kubernetes 1.33.

Environment

CloudBees CI on modern cloud platforms - operations center version before 2.516.1.28665
Kubernetes cluster version 1.33 or higher

Resolution

This issue is resolved in CloudBees CI version 2.516.1.28665.

CloudBees CI version 2.516.1.28665 introduced support for Kubernetes 1.33 as per Supported platforms for CloudBees CI on modern cloud platforms.

Tested product/plugin versions

Error occurs with CloudBees CI on modern cloud platforms - operations center version 2.504.3.28224, on GKE 1.33.5, and was resolved after upgrading CloudBees CI to version 2.516.3.29358.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.