CloudBees CI release notes

CasC Export now escapes variable expressions. However, variable expressions are not replaced when imported, unless a new configuration is set as pass thru.

This fix introduces a breaking change and any bundle using the variable resolution will stop working. To continue to use and resolve variables in your bundle, configure your CloudBees CI instance before loading your CasC bundles. To configure your CloudBees CI instance do one of the following:

For more information, refer to Creating items with CasC for controllers or Creating items with CasC for the operations center.

Pod Security Policy (PSP) was deprecated in Kubernetes 1.21 and removed from Kubernetes 1.25. As an alternative, you can enforce Pod Security Standards by using Pod Security Admission (PSA). Refer to Pod Security Admission for CloudBees CI on modern cloud platforms for more information.

Operations center sign-on (SSO) is not working from controllers connected using WebSocket. An error is displayed when attempting to log in that the public key is missing.

The CloudBees CasC Server plugin 2.0 upgrade introduces bundle branch and tag support. The plugin update changes the folder structure within JENKINS_HOME that stores the Configuration as Code (CasC) for Controllers for controller bundles. Due to the change to this folder structure, your existing bundles must be migrated. For more information on migrating your bundles, refer to Migrating Bundles.

The Promoted Builds plugin was removed from the CloudBees Assurance Program (CAP). It was previously integrated with the Operations Center Context plugin.

The Java library used to access Kubernetes, fabric8 Kubernetes-client, has been upgraded from 5.x to 6.x.

This new Java library version enables customers to provide CustomResourceDefinitions (CRDs) to the provisioning lifecycle, even if they are not part of the client Java model.

This update has no impact for customers who do not use the YAML field under Advanced configuration on the controller configuration screen in the Operations center. For customers using the YAML field under Advanced configuration, this update has the following impact:

For more information about this upgrade, refer to this knowledge base article, The apiVersion on a resource being deserialized is required after upgrading Kubernetes-client 6.x. The article also contains a script that you can run to check for invalid configurations. The configurations listed in the output of this script should be fixed by providing a valid apiVersion.

If you have questions about this upgrade, contact CloudBees Support for assistance.