From dcce80b741c2b8315de5aaaa2aa333956f00eb9d Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 12:51:01 +0100 Subject: [PATCH 1/6] Update RN texts --- artifacts/attributes.adoc | 4 +--- .../ref-release-notes-breaking-changes.adoc | 1 + ...ease-notes-deprecated-functionalities.adoc | 2 ++ .../ref-release-notes-fixed-issues.adoc | 17 +++++++++++++++ .../ref-release-notes-known-issues.adoc | 3 ++- .../ref-release-notes-new-features.adoc | 16 +++++++------- .../ref-release-notes-technology-preview.adoc | 21 +++++++++++-------- 7 files changed, 42 insertions(+), 22 deletions(-) diff --git a/artifacts/attributes.adoc b/artifacts/attributes.adoc index f43ce5031..414f2057e 100644 --- a/artifacts/attributes.adoc +++ b/artifacts/attributes.adoc @@ -13,7 +13,7 @@ :product-version: 1.4 :product-bundle-version: 1.4.0 :product-chart-version: 1.4.0 -:product-backstage-version: 1.31.3 +:product-backstage-version: 1.32.6 :product-custom-resource-type: Backstage :rhdeveloper-name: Red Hat Developer :rhel: Red Hat Enterprise Linux @@ -46,8 +46,6 @@ :rhsso: RHSSO :rhbk-brand-name: Red Hat Build of Keycloak :rhbk: RHBK -:rhtap-brand-name: Red Hat Trusted Application Pipeline -:rhtap-very-short: RHTAP // RHTAP information :rhtap-version: 1.3 diff --git a/modules/release-notes/ref-release-notes-breaking-changes.adoc b/modules/release-notes/ref-release-notes-breaking-changes.adoc index 112a76108..b4446117e 100644 --- a/modules/release-notes/ref-release-notes-breaking-changes.adoc +++ b/modules/release-notes/ref-release-notes-breaking-changes.adoc @@ -9,6 +9,7 @@ This section lists breaking changes in {product} {product-version}. Prom-client metrics have been removed and replaced with OpenTelemetry metrics. As a result, the metrics port has changed from `7007` to `9464`. Deprecated metrics have also been removed. If you had dependencies on these, ensure your prometheus queries are updated. For further information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/monitoring_and_logging/index#assembly-rhdh-observability[Monitoring and logging] + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4572[RHIDP-4572] diff --git a/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc b/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc index dac0fde51..22fc8dd86 100644 --- a/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc +++ b/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc @@ -9,6 +9,7 @@ This section lists deprecated functionalities in {product} {product-version}. The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plugin has been deprecated and will be removed in the next release. You can link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_ansible_plug-ins_for_red_hat_developer_hub/index[use Ansible plug-ins for {product-very-short}] instead. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-3545[RHIDP-3545] @@ -17,6 +18,7 @@ The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plug With this update, you can evaluate your platform's log forwarding solutions to align with your security and compliance needs. Most of these solutions offer configurable options to minimize the loss of logs in the event of an outage. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4913[RHIDP-4913] diff --git a/modules/release-notes/ref-release-notes-fixed-issues.adoc b/modules/release-notes/ref-release-notes-fixed-issues.adoc index 33bb4c36b..a84fef61d 100644 --- a/modules/release-notes/ref-release-notes-fixed-issues.adoc +++ b/modules/release-notes/ref-release-notes-fixed-issues.adoc @@ -13,6 +13,7 @@ Previously, the GitHub issues plugin defaulted to using the first GitHub integra Now, GitHub issues plugin supports multiple GitHub integration hosts. It uses the well-known entity slug annotation `backstage.io/source-location` or `backstage.io/managed-by-location` to determine the appropriate GitHub integration for a component. If no integration matches the slug, the first GitHub integration is selected, maintaining the previous behavior. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-2727[RHIDP-2727] @@ -24,6 +25,7 @@ Previously, some API documentation defined in the 3scale backend plugin was not With this update, all API documentation defined in the 3scale backend plugin is imported and merged in the {product-very-short}. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-2903[RHIDP-2903] @@ -35,6 +37,7 @@ Previously, when deploying with the Helm Chart, there could be a mismatch betwee This update fixes this issue by ensuring no mismatch between those values. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-3115[RHIDP-3115] @@ -46,6 +49,7 @@ Previously, disabling the Role-Based Access Control (RBAC) backend plugin create With this update, disabling the RBAC backend plugin no longer creates roles and permission policies. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-3849[RHIDP-3849] @@ -57,6 +61,7 @@ Before this update, repositories were added to the {product-short} from various With this update, an alert on the deletion icon notifies the user to modify the source (either the `catalog-info` within the repository or the `app-config.yaml` file if the file originates from there) to remove the catalog entity. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-3931[RHIDP-3931] @@ -68,6 +73,7 @@ Before this update, the custom resources in Kubernetes configuration were pre-co This update removes the pre-configured custom resources from the Kubernetes configuration. Therefore, users can customize resources to the Kubernetes configuration based on their requirements, preventing unrelated warnings from appearing. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4240[RHIDP-4240] @@ -79,6 +85,7 @@ Before this update, Role-Based Access Control (RBAC) backend plugin broke in Bac This update resolves compatibility issues with RBAC backend plugin on Backstage versions `1.31` and `1.32` without displaying any errors. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4241[RHIDP-4241] @@ -90,6 +97,7 @@ Before this update, the backstage instance failed to start in version `5.1.0`, s With this update, the Role-Based Access Control (RBAC) Backend plugin now starts successfully in version `5.1.0` without displaying any errors. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4732[RHIDP-4732] @@ -101,6 +109,7 @@ Before this update, scaling the deployment to more than one pod caused Role-Base With this update, RBAC roles are now properly synced across all pods, with Redis cache and traffic routing configured to ensure consistency across the deployment. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4734[RHIDP-4734] @@ -112,6 +121,7 @@ Previously, the CLI examined the dependencies of embedded packages during the ex This update changes the parent directory that the {{require}} uses from the monorepo root to the embedded package. Therefore, the dependent package found is the dependency that is most relevant to the embedded package. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5014[RHIDP-5014] @@ -124,6 +134,9 @@ Previously, the CLI failed with a message that native modules are not supported. This update introduces two new CLI flags that help dynamic plugin developers handle native modules. Both flags accept a list of packages. The `--suppress-native-package` flag does not require the native module at runtime. It replaces the native module with an empty package that displays an error. The `--allow-native-package` flag instructs the CLI to allow the native package during checks, and tests a plugin that uses a native module. + + + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5062[RHIDP-5062] @@ -135,6 +148,7 @@ Previously, the feature to report a documentation (TechDoc) issue failed. Theref With this update, users can select texts when reporting a documentation (TechDoc) issue. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5120[RHIDP-5120] @@ -146,6 +160,7 @@ Previously, the `export-dynamic-plugin` failed with an error that the `stdout ma With this update, the CLI redirects the output of the {{yarn install}} command it performs during the export process to a file. Therefore, a successful completion of the {{yarn install}} command and verification of the `export-dynamic-plugin`, cleans up the file. The file is available for troubleshooting when the dynamic plugin validation checks fail. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5136[RHIDP-5136] @@ -157,6 +172,7 @@ Previously, exporting a plugin that has not been updated to a newer backstage ve With this update, an `--ignore-version-check` flag accepts a list of package names causing the CLI to selectively ignore the semver check the CLI performs when evaluating the plugin package dependencies. Therefore, a plugin that has not been updated works because it relies on unchanged interfaces and functions. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5141[RHIDP-5141] @@ -166,6 +182,7 @@ With this update, an `--ignore-version-check` flag accepts a list of package nam With this update, you are now required to enable both `./dynamic-plugins/dist/backstage-community-tech-radar` and `./dynamic-plugins/dist/backstage-community-tech-radar-backend-dynamic` to use the Tech Radar plugin. You must configure additional settings depending on where you choose to load the JSON data for the plugin. + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5297[RHIDP-5297] diff --git a/modules/release-notes/ref-release-notes-known-issues.adoc b/modules/release-notes/ref-release-notes-known-issues.adoc index 721005c44..cd56e912f 100644 --- a/modules/release-notes/ref-release-notes-known-issues.adoc +++ b/modules/release-notes/ref-release-notes-known-issues.adoc @@ -7,7 +7,8 @@ This section lists known issues in {product} {product-version}. [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 * link:https://issues.redhat.com/browse/RHIDP-3396[RHIDP-3396] diff --git a/modules/release-notes/ref-release-notes-new-features.adoc b/modules/release-notes/ref-release-notes-new-features.adoc index a6eafddd5..811ff0408 100644 --- a/modules/release-notes/ref-release-notes-new-features.adoc +++ b/modules/release-notes/ref-release-notes-new-features.adoc @@ -42,26 +42,27 @@ Identify the flavor of Backstage that is running. Default value: `rhdh` [id="feature-rhidp-4419"] -== Ability to manage PVCs in RHDH Operator +== [Doc] Document how to manage PVCs in RHDH Operator + += 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 link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/administration_guide_for_red_hat_developer_hub/index#proc-rhdh-deployment-config_assembly-admin-templates[Persistent Volume Claim (PVC)]. - [id="feature-rhidp-4805"] == Authenticating with {rhbk-brand-name} With this update, you can use {rhbk-brand-name} as an authentication provider. The Keycloak plugin will now support ingesting users and groups with {rhbk-brand-name}. For more details, see link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html-single/getting_started_guide/index#getting-started-zip-start-red-hat-build-of-keycloak[Authentication with {rhbk-brand-name}]. - [id="feature-rhidp-4806"] -== Ability to install third-party plugins in {product-very-short} +== [Docs] Document how to install 3rd party plugins to RHDH + += Ability to install third-party plugins in {product-very-short} You can now install third-party plugins in {product} without rebuilding the {product-very-short} application. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/introduction_to_plugins/index[Third party plugins]. - [id="feature-rhidp-4853"] == Plugins with updated scope @@ -189,7 +190,4 @@ With this update, the `backstage-plugin-catalog-backend-module-logs` is enabled [id="feature-rhidp-5218"] == {rhsso-brand-name} `7.6` is deprecated as an authentication provider -{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`. - - - +{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`. \ No newline at end of file diff --git a/modules/release-notes/ref-release-notes-technology-preview.adoc b/modules/release-notes/ref-release-notes-technology-preview.adoc index 31bcc50f5..4b014e7e6 100644 --- a/modules/release-notes/ref-release-notes-technology-preview.adoc +++ b/modules/release-notes/ref-release-notes-technology-preview.adoc @@ -59,16 +59,16 @@ The following tables list products and their versions compatible with {product-s | 1.2.0 | `@backstage/core-app-api` -| 1.15.0 +| 1.15.1 | `@backstage/core-components` -| 0.15.0 +| 0.15.1 | `@backstage/core-plugin-api` -| 1.9.4 +| 1.10.0 | `@backstage/integration-react` -| 1.1.32 +| 1.2.0 |=== .Backend plugin packages compatibility matrix @@ -78,22 +78,24 @@ The following tables list products and their versions compatible with {product-s | Version | `@backstage/backend-app-api` -| 1.0.0 +| 1.0.1 + | `@backstage/backend-defaults` -| 0.5.0 +| 0.5.2 | `@backstage/backend-dynamic-feature-service` -| 0.4.1 +| 0.4.4 + | `@backstage/backend-plugin-api` -| 1.0.0 +| 1.0.1 | `@backstage/catalog-model` | 1.7.0 | `@backstage/cli-node` -| 0.2.8 +| 0.2.9 | `@backstage/config` | 1.2.0 @@ -101,6 +103,7 @@ The following tables list products and their versions compatible with {product-s | `@backstage/config-loader` | 1.9.1 |=== + .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5070[RHIDP-5070] From 6385ef4a4febb536b9ea0297fe9aa14436cc3723 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 13:17:42 +0100 Subject: [PATCH 2/6] Update RN texts --- modules/release-notes/ref-release-notes-new-features.adoc | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/modules/release-notes/ref-release-notes-new-features.adoc b/modules/release-notes/ref-release-notes-new-features.adoc index 811ff0408..d0f3d15bf 100644 --- a/modules/release-notes/ref-release-notes-new-features.adoc +++ b/modules/release-notes/ref-release-notes-new-features.adoc @@ -42,9 +42,7 @@ Identify the flavor of Backstage that is running. Default value: `rhdh` [id="feature-rhidp-4419"] -== [Doc] Document how to manage PVCs in RHDH Operator - -= Ability to manage PVCs in RHDH Operator +== 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 link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/administration_guide_for_red_hat_developer_hub/index#proc-rhdh-deployment-config_assembly-admin-templates[Persistent Volume Claim (PVC)]. @@ -55,9 +53,7 @@ For more information, see link:https://docs.redhat.com/en/documentation/red_hat_ With this update, you can use {rhbk-brand-name} as an authentication provider. The Keycloak plugin will now support ingesting users and groups with {rhbk-brand-name}. For more details, see link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html-single/getting_started_guide/index#getting-started-zip-start-red-hat-build-of-keycloak[Authentication with {rhbk-brand-name}]. [id="feature-rhidp-4806"] -== [Docs] Document how to install 3rd party plugins to RHDH - -= Ability to install third-party plugins in {product-very-short} +== Ability to install third-party plugins in {product-very-short} You can now install third-party plugins in {product} without rebuilding the {product-very-short} application. From b091194afd8bb6edba1c88d74db7563ed6846c31 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 15:37:24 +0100 Subject: [PATCH 3/6] Update RN texts --- .../ref-release-notes-deprecated-functionalities.adoc | 6 ++++++ .../release-notes/ref-release-notes-technology-preview.adoc | 6 ++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc b/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc index 22fc8dd86..ea09a89a9 100644 --- a/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc +++ b/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc @@ -22,5 +22,11 @@ With this update, you can evaluate your platform's log forwarding solutions to a .Additional resources * link:https://issues.redhat.com/browse/RHIDP-4913[RHIDP-4913] +[id="deprecated-functionality-rhidp-5218"] +== {rhsso-brand-name} `7.6` is deprecated as an authentication provider +{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`. + +.Additional resources +* link:https://issues.redhat.com/browse/RHIDP-5218[RHIDP-5218] \ No newline at end of file diff --git a/modules/release-notes/ref-release-notes-technology-preview.adoc b/modules/release-notes/ref-release-notes-technology-preview.adoc index 4b014e7e6..edffabfd8 100644 --- a/modules/release-notes/ref-release-notes-technology-preview.adoc +++ b/modules/release-notes/ref-release-notes-technology-preview.adoc @@ -80,14 +80,12 @@ The following tables list products and their versions compatible with {product-s | `@backstage/backend-app-api` | 1.0.1 - | `@backstage/backend-defaults` | 0.5.2 | `@backstage/backend-dynamic-feature-service` | 0.4.4 - | `@backstage/backend-plugin-api` | 1.0.1 @@ -107,5 +105,5 @@ The following tables list products and their versions compatible with {product-s .Additional resources * link:https://issues.redhat.com/browse/RHIDP-5070[RHIDP-5070] - - +== Added notification backend plugins +With this update, {product-short} includes the `@backstage/plugin-notification-backend` plugins to manage and streamline notification delivery. From dc002ea4a482a09049422d3d24170ea0d35179d7 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 15:38:40 +0100 Subject: [PATCH 4/6] Update RN texts --- modules/release-notes/ref-release-notes-technology-preview.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/release-notes/ref-release-notes-technology-preview.adoc b/modules/release-notes/ref-release-notes-technology-preview.adoc index edffabfd8..59ddb00f7 100644 --- a/modules/release-notes/ref-release-notes-technology-preview.adoc +++ b/modules/release-notes/ref-release-notes-technology-preview.adoc @@ -106,4 +106,4 @@ The following tables list products and their versions compatible with {product-s * link:https://issues.redhat.com/browse/RHIDP-5070[RHIDP-5070] == Added notification backend plugins -With this update, {product-short} includes the `@backstage/plugin-notification-backend` plugins to manage and streamline notification delivery. +With this update, {product-short} includes the Signals (frontend), Notifications (backend), Notifications (frontend), and Notifications Module Email plugins to manage and streamline notification delivery. \ No newline at end of file From 93e35a9d029e62c547c783589cbc28921edb4da9 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 16:50:52 +0100 Subject: [PATCH 5/6] Update RN texts --- .../release-notes/ref-release-notes-known-issues.adoc | 7 +++++++ .../release-notes/ref-release-notes-new-features.adoc | 7 +------ .../ref-release-notes-technology-preview.adoc | 9 ++++++++- 3 files changed, 16 insertions(+), 7 deletions(-) diff --git a/modules/release-notes/ref-release-notes-known-issues.adoc b/modules/release-notes/ref-release-notes-known-issues.adoc index cd56e912f..7b9be2e01 100644 --- a/modules/release-notes/ref-release-notes-known-issues.adoc +++ b/modules/release-notes/ref-release-notes-known-issues.adoc @@ -13,5 +13,12 @@ Permissions associated only with front-end plugins do not appear in the UI becau .Additional resources * link:https://issues.redhat.com/browse/RHIDP-3396[RHIDP-3396] +[id="known-issue-rhidp-5342"] +== Unable to run two {product-very-short} replicas on different nodes due to Multi-Attach errors on dynamic plugins root PVC +If you are deploying {product-short} using the Helm Chart, it is currently impossible to have two 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] diff --git a/modules/release-notes/ref-release-notes-new-features.adoc b/modules/release-notes/ref-release-notes-new-features.adoc index d0f3d15bf..a08b714b5 100644 --- a/modules/release-notes/ref-release-notes-new-features.adoc +++ b/modules/release-notes/ref-release-notes-new-features.adoc @@ -181,9 +181,4 @@ Two plugins previously under the @janus-idp scope have moved to @red-hat-develop [id="feature-rhidp-5156"] == 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`. - -[id="feature-rhidp-5218"] -== {rhsso-brand-name} `7.6` is deprecated as an authentication provider - -{rhsso-brand-name} ({rhsso}) `7.6` is deprecated as an authentication provider. You can continue to use {rhsso} until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to {rhbk-brand-name} `v24`. \ No newline at end of file +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`. \ No newline at end of file diff --git a/modules/release-notes/ref-release-notes-technology-preview.adoc b/modules/release-notes/ref-release-notes-technology-preview.adoc index 59ddb00f7..da0d00110 100644 --- a/modules/release-notes/ref-release-notes-technology-preview.adoc +++ b/modules/release-notes/ref-release-notes-technology-preview.adoc @@ -106,4 +106,11 @@ The following tables list products and their versions compatible with {product-s * link:https://issues.redhat.com/browse/RHIDP-5070[RHIDP-5070] == Added notification backend plugins -With this update, {product-short} includes the Signals (frontend), Notifications (backend), Notifications (frontend), and Notifications Module Email plugins to manage and streamline notification delivery. \ No newline at end of file +With this update, {product-short} includes the following dynamic plugins to manage and streamline notification delivery: + +* `https://npmjs.com/package/@backstage/plugin-signals/v/0.0.11[@backstage/plugin-signals]` +* `https://npmjs.com/package/@backstage/plugin-notifications-backend/v/0.4.2[@backstage/plugin-notifications-backend]` +* `https://npmjs.com/package/@backstage/plugin-notifications/v/0.3.2[@backstage/plugin-notifications]` +* `https://npmjs.com/package/@backstage/plugin-notifications-backend-module-email/v/0.3.2[@backstage/plugin-notifications-backend-module-email]` + +These plugins are disabled by default. \ No newline at end of file From 098e91fc6481d82c900ce1e72967dc83aeba0166 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 18 Dec 2024 16:57:27 +0100 Subject: [PATCH 6/6] Update RN texts --- modules/release-notes/ref-release-notes-known-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/release-notes/ref-release-notes-known-issues.adoc b/modules/release-notes/ref-release-notes-known-issues.adoc index 7b9be2e01..7b97637c9 100644 --- a/modules/release-notes/ref-release-notes-known-issues.adoc +++ b/modules/release-notes/ref-release-notes-known-issues.adoc @@ -16,7 +16,7 @@ Permissions associated only with front-end plugins do not appear in the UI becau [id="known-issue-rhidp-5342"] == Unable to run two {product-very-short} replicas on different nodes due to Multi-Attach errors on dynamic plugins root PVC -If you are deploying {product-short} using the Helm Chart, it is currently impossible to have two 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. +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.