Operations Center Parent 3.0.74

RELEASED: Public: February 21, 2024

New features

Add support for operations-center-context triggerRemoteJob step (BEE-43961): Added support for the operations-center-context triggerRemoteJob step.
Introduction of a concrete type for controller exposure (BEE-44367): Before this update, the operations center would dynamically change the behavior of exposing a controller based on a runtime lookup to detect if the underlying Kubernetes infrastructure was OpenShift. However, this dynamic check could lead to the creation of an Ingress object for a controller instead of Route.

After this update, the type needs to be set when you configure the Kubernetes endpoint. The existing configuration will migrate to auto detect, but attempts will be made to replace it with the correct type.

The Configuration as Code bundles now need to be updated to specify the concrete type of service exposure method and for Ingress types, such as ingressClass and IngressAnnotations to be on the ContainerMasterProvisioningDescriptor.

View OpenShift CasC snippet:

====

masterprovisioning:
  kubernetes:
    clusterEndpoints:
      - id: "myEndpoint"
        name: "openshift"▼

becomes:

masterprovisioning:
  kubernetes:
    clusterEndpoints:
    - id: "myEndpoint"
      name: "openshift"
      serviceExposure: "openShiftRoute"▼

View Generic Kubernetes CasC snippet:

====

masterprovisioning:
  kubernetes:
    clusterEndpoints:
    - id: "myEndpoint"
      ingressAnnotations: |-
        key1: value1
        key2: value2
      ingressClass: "myingressclass"
      name: "kubernetes"▼

becomes:

masterprovisioning:
  kubernetes:
    clusterEndpoints:
    - id: "myEndpoint"
      name: "kubernetes"
      serviceExposure:
        ingress:
          ingressAnnotations: |-
            key1: value1
            key2: value2
          ingressClass: "myingressclass"▼

Feature enhancements

None.

Resolved issues

Remote copy artifact fails, if the file group ID exceeds the limit (> 2097151) (BEE-43452)

When the archived artifact is copied from a local/remote job step, the step fails and is not copied if the file group ID exceeds the limit (> 2097151).

This issue is resolved. Now, you can use group IDs that exceed the limits and successfully perform the copy.

Internal changes to streamline development. Not user visible. (BEE-45053)(BEE-45064)

Known issues

None.

Upgrade notes

None.