Chapter 1. New features
This section highlights new features in Red Hat Developer Hub 1.4.
1.1. Added an individual mountPath
This update adds an additional individual mountPath
for extra configmaps or secrets.
1.2. PersistentVolumeClaims
support is available
With this update, PersistentVolumeClaims
(PVC) support is available.
1.3. Added Configuration Profiles
With this update, there are additional configuration profiles.
1.4. Enhanced use of kube-rbac-proxy
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.
1.5. Identifying the Backstage flavor for plugins
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:
app-config.yaml
fragment with the developerhub.flavor
field
developerHub: flavor: <flavor>;
flavor
-
Identify the flavor of Backstage that is running. Default value:
rhdh
1.6. Ability to manage PVCs in RHDH Operator
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 Persistent Volume Claim (PVC).
1.7. Authenticating with Red Hat Build of Keycloak
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 Authentication with Red Hat Build of Keycloak.
1.8. Ability to install third-party plugins in RHDH
You can now install third-party plugins in Red Hat Developer Hub without rebuilding the RHDH application.
For more information, see Third party plugins.
1.9. The catalog backend module logs plugin is enabled
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
.