Release notes for 1.8

themr0c · themr0c · commit c2452b43e80d · 2025-11-10T10:27:51.000+01:00
Signed-off-by: Fabrice Flore-Thébault &lt;ffloreth@redhat.com&gt;
diff --git a/modules/release-notes/ref-release-notes-breaking-changes.adoc b/modules/release-notes/ref-release-notes-breaking-changes.adoc
@@ -5,6 +5,49 @@
 
 This section lists breaking changes in {product} {product-version}.
 
+[id="removed-functionality-rhidp-5309"]
+== Argo CD, Tekton, and Topology plugins require the Kubernetes Frontend and Kubernetes Backend plugins
+
+With this update, the Argo CD, Tekton, and Topology plugins requires the Kubernetes Frontend and Kubernetes Backend plugins. Before this update, these plugins depended only on the Kubernetes Backend plugin, and the feature provided by the Kubernetes Frontend plugin where provided by the removed `@janus-idp/shared-react` package.
+
+.Procedure
+. Enable the Kubernetes Frontend and Kubernetes Backend plugins.
++
+[source,yaml]
+----
+global:
+  dynamic:
+    plugins:
+      - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes
+        disabled: false
+      - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic
+        disabled: false
+----
+
+. The Kubernetes Frontend plugin shows automatically a *Kubernetes* tab for Software Catalog entities with the annotation `backstage.io/kubernetes-id` or `backstage.io/kubernetes-namespace`.
++
+Optionally, to hide the *Kubernetes* tab in the Software Catalog, disable the feature with this dynamic plugin configuration:
++
+[source,yaml]
+----
+global:
+  dynamic:
+    plugins:
+      - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes
+        disabled: false
+        pluginConfig:
+          dynamicPlugins:
+            frontend:
+              backstage.plugin-kubernetes:
+                mountPoints: []
+      - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic
+        disabled: false
+----
+
+
+
+.Additional resources
+* link:https://issues.redhat.com/browse/RHIDP-5309[RHIDP-5309]
+
 
-None.
 
diff --git a/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc b/modules/release-notes/ref-release-notes-deprecated-functionalities.adoc
@@ -5,23 +5,15 @@
 
 This section lists deprecated functionalities in {product} {product-version}.
 
-[id="deprecated-functionality-rhidp-6917"]
-== Backstage CR versions `v1alpha1` and `v1alpha2`
+[id="deprecated-functionality-rhidp-9180"]
+== OCM Plugins are deprecated
 
-Backstage CR versions `v1alpha1` and `v1alpha2` are deprecated in 1.7 and will be removed in 1.9
+The Open Cluster Management (OCM) plugins integrates your {product} instance with the MultiClusterHub and MultiCluster engines of OCM.
+The OCM plugins are deprecated as of RHDH 1.8, and will be removed in a future release. 
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHIDP-6917[RHIDP-6917]
+* link:https://issues.redhat.com/browse/RHIDP-9180[RHIDP-9180]
 
-[id="deprecated-functionality-rhidp-8525"]
-== Deprecation of Bundled Plugin Wrappers
 
-To enhance performance, decrease image size, and reduce maintenance, the method of including &#34;wrapped&#34; dynamic plugins within the main {product} container image is being deprecated as of release 1.7.0. We are transitioning to a model where all dynamic plugins will be distributed as independent OCI artifacts.
 
-For the 1.7.0 release, this is a deprecation notice only; there are no breaking changes, and all previously bundled plugins will continue to be bundled. However, we encourage customers to prepare for the removal of wrappers in a future release by beginning to use the new OCI artifacts in 1.8.0. Documentation will be updated to guide this migration.
-
-For more information, see {installing-and-viewing-plugins-book-link}#proc-load-plugin-oci-image_assembly-install-third-party-plugins-rhdh[Loading a plugin packaged as an OCI image].
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHIDP-8525[RHIDP-8525]
diff --git a/modules/release-notes/ref-release-notes-fixed-issues.adoc b/modules/release-notes/ref-release-notes-fixed-issues.adoc
@@ -1,153 +1,97 @@
 :_content-type: REFERENCE
+
 [id="fixed-issues"]
 = Fixed issues
 
 This section lists issues fixed in {product} {product-version}.
 
-== Fixed issues in 1.7.0
+== Fixed issues in 1.8.0
 
-[id="bug-fix-rhidp-6536"]
-=== Improved keyboard accessibility
+[id="bug-fix-rhdhbugs-1000"]
+===  Improved startup speed with updated init container image pull policy for {product-short} Helm Chart
 
-In this release, various fixes and improvements have been made to improve the keyboard accessibility in {product}.
+With this update, the pull policy for the init container image of the {product-short} Helm Chart was changed from `Always` to `IfNotPresent`. This change reduces the repeated download time during startup of the container image, which is approximately 2.5 GB, thereby significantly improving startup speed for users.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHIDP-6536[RHIDP-6536]
+* link:https://issues.redhat.com/browse/RHDHBUGS-1000[RHDHBUGS-1000]
 
 
-[id="bug-fix-rhdhbugs-249"]
-=== Fixed `techdocs-module-addons-contrib` plugin not displayed as preinstalled plugin
+[id="bug-fix-rhdhbugs-1028"]
+===  Improved Authentication for Self-Hosted Enterprise SCM Providers
 
-Previously, the `techdocs-module-addons-contrib` plugin was not displayed as preinstalled in Extensions. With this update, the plugin is displayed as preinstalled.
-
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-249[RHDHBUGS-249]
-
-
-[id="bug-fix-rhdhbugs-322"]
-=== Excessive queries to the `relations` database table from the `rbac-backend` plugin
+Previously, actions requiring access to a self-hosted enterprise SCM provider failed, returning an error that no authentication provider was available for the specified host.
 
-Before this update, excessive queries from the `rbac-backend` plugin to the `relations` database table caused performance issues. As a consequence, users experienced slow performance. With this release, the RBAC backend plugin has been optimized to improve performance by preventing excessive queries to the &#39;relations&#39; database table. 
+With this update, the SCM integration correctly identifies and uses the configured authentication provider for the corresponding enterprise host.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-322[RHDHBUGS-322]
+* link:https://issues.redhat.com/browse/RHDHBUGS-1028[RHDHBUGS-1028]
 
 
-[id="bug-fix-rhdhbugs-503"]
-=== The Operator reverts the number of replicas set automatically by a Horizontal Pod Autoscaler (HPA)
-
-Previously the {product-very-short} Operator enforced `replicas: 1` from its default deployment config, which overrode scaling decisions. 
+[id="bug-fix-rhdhbugs-2003"]
+=== Customizable image names for job and data index services in {product-short} Helm Chart
 
-With this update, `replicas: 1` is removed from the default deployment profile and the DB-statefulset manifest. 
-
-This update allows HPA to control scaling as expected, so that {product-very-short} instances can now scale dynamically with HPA without being reset by the operator.
+Previously, when deploying the {product-short} Helm Chart with the Orchestrator enabled, it was not possible to customize the image names of the job and data index services, for example in disconnected environments. Setting the `orchestrator.sonataflowPlatform.jobServiceImage` and `orchestrator.sonataflowPlatform.dataIndexImage` would return a schema validation error from Helm. This update fixes this issue.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-503[RHDHBUGS-503]
+* link:https://issues.redhat.com/browse/RHDHBUGS-2003[RHDHBUGS-2003]
 
 
-[id="bug-fix-rhdhbugs-512"]
-=== Improved error messaging for bulk imports
+[id="bug-fix-rhdhbugs-2020"]
+=== Network policy installation fix for {product-short} RHDH Helm Chart with Orchestrator flavor
 
-Before this update, when users selected 100 or more repositories simultaneously, the create pull request action could fail with a generic error message. In this release, we provide a more informative error message when creating pull requests for multiple repositories. This bug fix helps users to understand the issue by providing more information about what caused the error.
+Before this update, the {product-short} RHDH Helm Chart would not install Network Policies when the Orchestrator flavor was deployed with `serverlessLogicOperator` disabled, preventing the {product-short} Pods from being completely available. This update fixes this situation by installing network policies unconditionally when the orchestrator is enabled.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-512[RHDHBUGS-512]
+* link:https://issues.redhat.com/browse/RHDHBUGS-2020[RHDHBUGS-2020]
 
 
-[id="bug-fix-rhdhbugs-622"]
-=== Excessive authorize requests generated by the RBAC backend API
+[id="bug-fix-rhdhbugs-2036"]
+=== Resolved SonataFlow Pod Crash Issue
 
-Before this update, excessive authorize requests in the REST API for creating/editing roles, permissions, and conditions in rbac-backend led to performance issues. With this release, the excessive authorization requests in the REST API have been fixed by reducing permissions to only &#39;user&#39; credentials. 
+In the new release, a timing problem during the RHDH 1.7 installation with Orchestrator plugins, affecting SonataFlow database provisioning, has been addressed. This issue caused SonataFlow pods to repeatedly enter the `CrashLoopBackOff` state, leading to delays and potential confusion for users. With this update, SonataFlow pods no longer encounter the `CrashLoopBackOff` state due to the database provisioning delay. This improvement enhances the user experience, as SonataFlow pods now start promptly, eliminating unnecessary wait times.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-622[RHDHBUGS-622]
+* link:https://issues.redhat.com/browse/RHDHBUGS-2036[RHDHBUGS-2036]
 
+== Fixed issues in 1.7.2
 
-[id="bug-fix-rhdhbugs-632"]
-=== Custom title not persisting on refresh of visited cards
-
-Previously, the custom title set via `app.title` in the _Top Visited_ and _Recently Visited_ cards did not persist after a page refresh, instead it defaulted back to _{product}_.
+[id="bug-fix-rhdhbugs-2117"]
+=== Fixed SCM integration failures for self-hosted enterprise SCM providers
 
-With this update, after each refresh, the cards correctly display the custom title defined in the `app.title` configuration.
-
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-632[RHDHBUGS-632]
-
-
-[id="bug-fix-rhdhbugs-834"]
-=== Fixed role name updates via API to correctly propagate to permissions, metadata, and conditions
+Before this update, the SCM integration failed due to lack of identification of the configured authentication provider for self-hosted enterprise SCM hosts. As a consequence, users experienced failed actions with self-hosted enterprise SCM providers due to missing authentication. 
 
-Previously, when a role name was updated using the RBAC API, existing permissions, conditions, and metadata were not updated and remained mapped to the old role name.
-With this update, role name changes are now correctly updated.
+With this release, the SCM integration now correctly uses the configured authentication provider for corresponding enterprise host. As a result, end users can now successfully perform actions requiring enterprise SCM access.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-834[RHDHBUGS-834]
+* link:https://issues.redhat.com/browse/RHDHBUGS-2117[RHDHBUGS-2117]
 
+== Fixed issues in 1.7.1
 
-[id="bug-fix-rhdhbugs-903"]
-=== Fixed role actions tooltip delay issue
+[id="bug-fix-rhdhbugs-1878"]
+=== Fixed incorrect version detection for local plugin updates
 
-Previously, tooltips on action icons in the Role list table of the Role-Based Access Control (RBAC) page were slow to appear on hover.
-
-This issue has been fixed, ensuring that tooltips now appear immediately when hovering over action icons in the RBAC page.
+Before this update, local plugins within the image were incorrectly detected for updates due to version misidentification. This led to users being unable to update local plugins from wrappers, resulting in outdated functionality. With this release, local plugin updates are now automatically detected, eliminating the need for manual adjustments and ensuring seamless plugin version updates for end users.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-903[RHDHBUGS-903]
+* link:https://issues.redhat.com/browse/RHDHBUGS-1878[RHDHBUGS-1878]
 
 
-[id="bug-fix-rhdhbugs-1110"]
-=== The Extensions catalog does not show an error when the backend plugin is not installed
-
-Previously, if the backend Extensions was not installed, {product-very-short} showed the skeleton &#34;forever&#34; instead of an error message.
+[id="bug-fix-rhdhbugs-2041"]
+=== Orchestrator plugin updated to 1.7.1
 
-With this update, the UI shows an empty state with a message to enable the backend plugin.
+Before this update, the latest Orchestrator feature set was unavailable because the release included the outdated Orchestrator plugin version `1.6`. This issue is resolved in {product-very-short} `1.7.1`. The Orchestrator plugin is now updated to version `1.7.1`, ensuring that users have access to the latest features and functionality.
 
 
-.Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-1110[RHDHBUGS-1110]
-
-
-[id="bug-fix-rhdhbugs-1139"]
-=== Fixed Profile dropdown showing Guest instead of user&#39;s name with OIDC authentication 
-
-Previously, the *Profile dropdown* in the Global Header showed `Guest` instead of the logged-in user’s display name when logging in using the OIDC authentication.
-
-With this update, the *Profile dropdown* now correctly displays the user&#39;s name by first checking `spec.profile.displayName`, then `metadata.title`, and finally falls back to the name shown on the *Profile card* in the *Settings* page if neither is available.
-
-
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-1139[RHDHBUGS-1139]
-
-
-[id="bug-fix-rhdhbugs-1162"]
-=== Excessive filter arguments generated by the RBAC backend `enforcerDelegate.getFilteredPolicy`
-
-Before this update, {product-very-short} performance was affected by the duplication of filter arguments in `enforcerDelegate.getFilteredPolicy`.  With this release, the duplication of filter arguments in `enforcerDelegate.ts` is avoided.
-
-
-.Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-1162[RHDHBUGS-1162]
-
-
-[id="bug-fix-rhdhbugs-1213"]
-=== Fixed Jenkins permissions not being displayed in RBAC UI
-
-Previously, Jenkins permissions were not exposed by Jenkins at `/api/jenkins/.well-known/backstage/permissions/metadata` with the change to `JenkinsBuilder`. As a result, RBAC UI did not display the permissions. In this release, users can configure Jenkins permissions by using the RBAC UI.
-
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-1213[RHDHBUGS-1213]
+* link:https://issues.redhat.com/browse/RHDHBUGS-2041[RHDHBUGS-2041]
 
 
 
diff --git a/modules/release-notes/ref-release-notes-known-issues.adoc b/modules/release-notes/ref-release-notes-known-issues.adoc
@@ -5,21 +5,61 @@
 
 This section lists known issues in {product} {product-version}.
 
-[id="known-issue-rhdhbugs-1979"]
-== Latest Orchestrator feature set is unavailable
+[id="known-issue-rhdhbugs-986"]
+== MUI v5 components might render with broken styles in non-bundled plugins
 
-This release includes the Orchestrator plugin version from `1.6`. As a result, the latest feature set is not yet available. The Orchestrator plugin will be updated to the latest feature set in a future release.
+Plugins that are not bundled with {product}, meaning not part of the {product} wrappers, might experience styling issues or broken visuals when using Material UI v5 components. 
 
+. Workaround
+* Add the following code to the plugin’s entry file, such as `workspaces/&lt;pluginId&gt;/plugins/&lt;pluginId&gt;/src/index.ts`:
++
+[source,javascript]
+----
+import { unstable_ClassNameGenerator as ClassNameGenerator } from &#39;@mui/material/className&#39;;
 
+ClassNameGenerator.configure(componentName =&gt; {
+  return componentName.startsWith(&#39;v5-&#39;)
+    ? componentName
+    : `v5-${componentName}`;
+});
+----
 
+// Source: https://docs.google.com/document/d/1cF-pRNY7duwD5JP8ACQVP24oJJw8ffphCzIgmyICcAM/edit?usp=sharing
 
 
+.Additional resources
+* link:https://issues.redhat.com/browse/RHDHBUGS-986[RHDHBUGS-986]
+
+[id="known-issue-rhdhbugs-664"]
+== Out-Of-Memory errors in the {product} Operator
+
+To resolve Out-Of-Memory errors in the {product} Operator, adjust memory settings manually:
+
+. Edit the deployment:
++
+---- 
+kubectl edit deployment rhdh-operator -n &lt;namespace&gt;
+----
 
+. In the editor, set the memory request to 1 GiB and the limit to 2 GiB:
++
+[source,yaml]
+----
+spec:
+  containers:
+  - name: rhdh-operator
+    resources:
+      requests:
+        memory: &#34;1G&#34;
+      limits:
+        memory: &#34;2G&#34;
+----
 
+. Reapply this change whenever the Operator is actively reconciled. The pod should become healthy, using about 1.07 GiB of memory.
 
 
 .Additional resources
-* link:https://issues.redhat.com/browse/RHDHBUGS-1979[RHDHBUGS-1979]
+* link:https://issues.redhat.com/browse/RHDHBUGS-664[RHDHBUGS-664]
 
 
 
diff --git a/modules/release-notes/ref-release-notes-new-features.adoc b/modules/release-notes/ref-release-notes-new-features.adoc
