diff --git a/modules/release-notes/ref-release-notes-breaking-changes.adoc b/modules/release-notes/ref-release-notes-breaking-changes.adoc index 301869995..e795ab36d 100644 --- a/modules/release-notes/ref-release-notes-breaking-changes.adoc +++ b/modules/release-notes/ref-release-notes-breaking-changes.adoc @@ -16,78 +16,78 @@ Prom-client metrics have been removed and replaced with OpenTelemetry metrics. A [id="removed-functionality-rhidp-4853"] == Plugins with updated scope -To upgrade from {product-very-short} 1.3 to 1.4, you must update your configuration to use the latest versions of the following plugins from the new scope. - -With this update, the following plugins, previously under the `@janus-idp` scope, have now been moved to the `@backstage-community` scope: - -[cols=2,%header] -|=== -| *RHDH 1.3 Plugin Name* -| *RHDH 1.4 Plugin Name* -|`@janus-idp/backstage-plugin-acr`|`@backstage-community/plugin-acr` -|`@janus-idp/backstage-plugin-acr`|`@backstage-community/plugin-acr` -|`@janus-idp/backstage-plugin-analytics-provider-segment`|`@backstage-community/plugin-analytics-provider-segment` -|`@janus-idp/backstage-plugin-jfrog-artifactory`|`@backstage-community/plugin-jfrog-artifactory` -|`@janus-idp/backstage-plugin-keycloak-backend`|`@backstage-community/plugin-catalog-backend-module-keycloak` -|`@janus-idp/backstage-plugin-nexus-repository-manager`|`@backstage-community/plugin-nexus-repository-manager` -|`@janus-idp/backstage-plugin-ocm`|`@backstage-community/plugin-ocm` -|`@janus-idp/backstage-plugin-ocm-backend`|`@backstage-community/plugin-ocm-backend` -|`@janus-idp/backstage-plugin-quay`|`@backstage-community/plugin-quay` -|`@janus-idp/backstage-plugin-rbac`|`@backstage-community/plugin-rbac` -|`@janus-idp/backstage-plugin-tekton`|`@backstage-community/plugin-tekton` -|`@janus-idp/backstage-plugin-topology`|`@backstage-community/plugin-topology` -|`@janus-idp/backstage-scaffolder-backend-module-quay`|`@backstage-community/plugin-scaffolder-backend-module-quay` -|`@janus-idp/backstage-scaffolder-backend-module-regex`|`@backstage-community/plugin-scaffolder-backend-module-regex` -|`@janus-idp/backstage-scaffolder-backend-module-servicenow`|`@backstage-community/plugin-scaffolder-backend-module-servicenow` -|`@janus-idp/backstage-scaffolder-backend-module-sonarqube`|`@backstage-community/plugin-scaffolder-backend-module-sonarqube` -|=== - -The following plugins, previously under the `@backstage` scope, have now been moved to the `@backstage-community` scope: -[cols=2,%header] -|=== -| *RHDH 1.3 Plugin Name* -| *RHDH 1.4 Plugin Name* -|`@backstage/plugin-azure-devops`|`@backstage-community/plugin-azure-devops` -|`@backstage/plugin-azure-devops-backend`|`@backstage-community/plugin-azure-devops-backend` -|`@backstage/plugin-dynatrace`|`@backstage-community/plugin-dynatrace` -|`@backstage/plugin-github-actions`|`@backstage-community/plugin-github-actions` -|`@backstage/plugin-github-issues`|`@backstage-community/plugin-github-issues` -|`@backstage/plugin-jenkins`|`@backstage-community/plugin-jenkins` -|`@backstage/plugin-jenkins-backend`|`@backstage-community/plugin-jenkins-backend` -|`@backstage/plugin-lighthouse`|`@backstage-community/plugin-lighthouse` -|`@backstage/plugin-sonarqube`|`@backstage-community/plugin-sonarqube` -|`@backstage/plugin-sonarqube-backend`|`@backstage-community/plugin-sonarqube-backend` -|`@backstage/plugin-tech-radar`|`@backstage-community/plugin-tech-radar` -|=== - -Two plugins previously under the `@janus-idp` scope have moved to `@red-hat-developer-hub` scope: - -[cols=2,%header] -|=== -| *RHDH 1.3 Plugin Name* -| *RHDH 1.4 Plugin Name* - -| `@janus-idp/backstage-plugin-bulk-import` -| `@red-hat-developer-hub/backstage-plugin-bulk-import` - -| `@janus-idp/backstage-plugin-bulk-import-backend` -| `@red-hat-developer-hub/backstage-plugin-bulk-import-backend` -|=== - -With the update to the plugin scope, the dynamic plugin configuration has also been modified. - -[cols=2,%header] -|=== -|*RHDH 1.3 Configuration*|*RHDH 1.4 Configuration* -|link:https://github.com/janus-idp/backstage-showcase/blob/release-1.3/dynamic-plugins.default.yaml[dynamic-plugins.default.yaml]|link:https://github.com/janus-idp/backstage-showcase/blob/release-1.4/dynamic-plugins.default.yaml[dynamic-plugins.default.yaml] -|=== - -.Procedure -* To upgrade from {product-very-short} 1.3 to {product-very-short} 1.4, you must update your configuration to use the latest versions of the plugins listed previously from the new scope. - -[NOTE] -==== -In addition to the previously provided tables, you can compare the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.4 CSV file] with the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.3/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.3 CSV file] to identify the changes in dynamic plugins. +To upgrade from {product-very-short} 1.3 to 1.4, you must update your configuration to use the latest versions of the following plugins from the new scope. + +With this update, the following plugins, previously under the `@janus-idp` scope, have now been moved to the `@backstage-community` scope: + +[cols=2,%header] +|=== +| *RHDH 1.3 Plugin Name* +| *RHDH 1.4 Plugin Name* +|`@janus-idp/backstage-plugin-acr`|`@backstage-community/plugin-acr` +|`@janus-idp/backstage-plugin-acr`|`@backstage-community/plugin-acr` +|`@janus-idp/backstage-plugin-analytics-provider-segment`|`@backstage-community/plugin-analytics-provider-segment` +|`@janus-idp/backstage-plugin-jfrog-artifactory`|`@backstage-community/plugin-jfrog-artifactory` +|`@janus-idp/backstage-plugin-keycloak-backend`|`@backstage-community/plugin-catalog-backend-module-keycloak` +|`@janus-idp/backstage-plugin-nexus-repository-manager`|`@backstage-community/plugin-nexus-repository-manager` +|`@janus-idp/backstage-plugin-ocm`|`@backstage-community/plugin-ocm` +|`@janus-idp/backstage-plugin-ocm-backend`|`@backstage-community/plugin-ocm-backend` +|`@janus-idp/backstage-plugin-quay`|`@backstage-community/plugin-quay` +|`@janus-idp/backstage-plugin-rbac`|`@backstage-community/plugin-rbac` +|`@janus-idp/backstage-plugin-tekton`|`@backstage-community/plugin-tekton` +|`@janus-idp/backstage-plugin-topology`|`@backstage-community/plugin-topology` +|`@janus-idp/backstage-scaffolder-backend-module-quay`|`@backstage-community/plugin-scaffolder-backend-module-quay` +|`@janus-idp/backstage-scaffolder-backend-module-regex`|`@backstage-community/plugin-scaffolder-backend-module-regex` +|`@janus-idp/backstage-scaffolder-backend-module-servicenow`|`@backstage-community/plugin-scaffolder-backend-module-servicenow` +|`@janus-idp/backstage-scaffolder-backend-module-sonarqube`|`@backstage-community/plugin-scaffolder-backend-module-sonarqube` +|=== + +The following plugins, previously under the `@backstage` scope, have now been moved to the `@backstage-community` scope: +[cols=2,%header] +|=== +| *RHDH 1.3 Plugin Name* +| *RHDH 1.4 Plugin Name* +|`@backstage/plugin-azure-devops`|`@backstage-community/plugin-azure-devops` +|`@backstage/plugin-azure-devops-backend`|`@backstage-community/plugin-azure-devops-backend` +|`@backstage/plugin-dynatrace`|`@backstage-community/plugin-dynatrace` +|`@backstage/plugin-github-actions`|`@backstage-community/plugin-github-actions` +|`@backstage/plugin-github-issues`|`@backstage-community/plugin-github-issues` +|`@backstage/plugin-jenkins`|`@backstage-community/plugin-jenkins` +|`@backstage/plugin-jenkins-backend`|`@backstage-community/plugin-jenkins-backend` +|`@backstage/plugin-lighthouse`|`@backstage-community/plugin-lighthouse` +|`@backstage/plugin-sonarqube`|`@backstage-community/plugin-sonarqube` +|`@backstage/plugin-sonarqube-backend`|`@backstage-community/plugin-sonarqube-backend` +|`@backstage/plugin-tech-radar`|`@backstage-community/plugin-tech-radar` +|=== + +Two plugins previously under the `@janus-idp` scope have moved to `@red-hat-developer-hub` scope: + +[cols=2,%header] +|=== +| *RHDH 1.3 Plugin Name* +| *RHDH 1.4 Plugin Name* + +| `@janus-idp/backstage-plugin-bulk-import` +| `@red-hat-developer-hub/backstage-plugin-bulk-import` + +| `@janus-idp/backstage-plugin-bulk-import-backend` +| `@red-hat-developer-hub/backstage-plugin-bulk-import-backend` +|=== + +With the update to the plugin scope, the dynamic plugin configuration has also been modified. + +[cols=2,%header] +|=== +|*RHDH 1.3 Configuration*|*RHDH 1.4 Configuration* +|link:https://github.com/janus-idp/backstage-showcase/blob/release-1.3/dynamic-plugins.default.yaml[dynamic-plugins.default.yaml]|link:https://github.com/janus-idp/backstage-showcase/blob/release-1.4/dynamic-plugins.default.yaml[dynamic-plugins.default.yaml] +|=== + +.Procedure +* To upgrade from {product-very-short} 1.3 to {product-very-short} 1.4, you must update your configuration to use the latest versions of the plugins listed previously from the new scope. + +[NOTE] +==== +In addition to the previously provided tables, you can compare the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.4/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.4 CSV file] with the link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/release-1.3/modules/dynamic-plugins/rhdh-supported-plugins.csv[RHDH 1.3 CSV file] to identify the changes in dynamic plugins. ==== diff --git a/modules/release-notes/ref-release-notes-known-issues.adoc b/modules/release-notes/ref-release-notes-known-issues.adoc index 624cf1592..919d04786 100644 --- a/modules/release-notes/ref-release-notes-known-issues.adoc +++ b/modules/release-notes/ref-release-notes-known-issues.adoc @@ -7,31 +7,18 @@ This section lists known issues in {product} {product-version}. [id="known-issue-rhidp-5344"] == Multi-Attached error for Volume (PVC) -Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node. - +Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node. + A possible workaround for the upgrade is to manually scale down the number of replicas to 0 before upgrading your Helm release. Or manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime. You can also leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node. .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5344[RHIDP-5344] -[id="known-issue-rhidp-5342"] -== [Helm] Cannot run two RHDH replicas on different nodes due to Multi-Attach errors on the dynamic plugins root PVC - -If you are deploying {product-short} using the Helm Chart, it is currently impossible to have 2 replicas running on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node. - -A possible workaround for the upgrade is to manually scale down the number of replicas to 0 before upgrading your Helm release. Or manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime. -You can also leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node. - - - -.Additional resources -* link:https://issues.redhat.com/browse/RHIDP-5342[RHIDP-5342] - [id="known-issue-rhidp-3396"] == Topology plugin permission is not displayed in the RBAC front-end UI -Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`). +Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`). .Additional resources diff --git a/modules/release-notes/ref-release-notes-new-features.adoc b/modules/release-notes/ref-release-notes-new-features.adoc index 6c267bb0e..bba839fa4 100644 --- a/modules/release-notes/ref-release-notes-new-features.adoc +++ b/modules/release-notes/ref-release-notes-new-features.adoc @@ -40,13 +40,13 @@ developerHub: `flavor`:: Identify the flavor of Backstage that is running. Default value: `rhdh` - [id="feature-rhidp-4419"] == Ability to manage Persistent Volume Claim (PVCs) in {product-very-short} 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 link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html-single/configuring/index#configuring-the-deployment[Configuring {product} deployment when using the Operator]. + [id="feature-rhidp-4805"] == Authenticating with {rhbk-brand-name}