Chapter 1. New features

This update adds an individual mountPath for extra ConfigMaps or Secrets.

With this update, PersistentVolumeClaims (PVC) support is available.

This update removes the kube-rbac-proxy sidecar container from the RHDH Operator Pod. This sidecar container protected the operator metrics endpoint. However, the main container now provides this functionality out-of-the-box. Removing this sidecar container allows for reducing the resources required to run the Operator.

With this update, you can use the developerHub.flavor field to identify whether plugins are running on RHDH, RHTAP, or vanilla Backstage, as shown in the following example:

developerHub:
  flavor: <flavor>

developerHub:
  flavor: <flavor>

You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the spec.application.extraFiles.pvcs field, while configuring RHDH Operator. For more information, see Configuring Red Hat Developer Hub deployment when using the Operator.

With this update, you can use Red Hat Build of Keycloak as an authentication provider. The Keycloak plugin will now support ingesting users and groups with Red Hat Build of Keycloak. For more details, see Authenticating with Red Hat Build of Keycloak.

You can now install third-party plugins in Red Hat Developer Hub without rebuilding the RHDH application.

For more information, see Installing third-party plugins in Red Hat Developer Hub.

With this update, the backstage-plugin-catalog-backend-module-logs is enabled and converted to a static plugin improving performance and stability. The dynamic plugin was disabled in version 1.3.

Google Kubernetes Engine (GKE) is out of Developer Preview and is now fully supported as of RHDH 1.4.

See the full list of supported platforms on the Life Cycle page.

Previously, running multi-replica RHDH with a Persistent Volume for the Dynamic Plugins cache was not possible due to potential write conflicts. This update mitigates that risk.