You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-deprecated-functionalities.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plug
16
16
[id="deprecated-functionality-rhidp-4913"]
17
17
== Audit log rotation is deprecated
18
18
19
-
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.
19
+
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.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-known-issues.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ This section lists known issues in {product} {product-version}.
7
7
[id="known-issue-rhidp-5344"]
8
8
== Multi-Attached error for Volume (PVC)
9
9
10
-
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.
11
-
10
+
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.
11
+
12
12
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.
13
13
14
14
@@ -18,7 +18,7 @@ A possible workaround for the upgrade is to manually scale down the number of re
18
18
[id="known-issue-rhidp-3396"]
19
19
== Topology plugin permission is not displayed in the RBAC front-end UI
20
20
21
-
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`).
21
+
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`).
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-new-features.adoc
+21-15Lines changed: 21 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,26 +27,32 @@ This update removes the `kube-rbac-proxy` sidecar container from the RHDH Operat
27
27
[id="feature-rhidp-4414"]
28
28
== Identifying Backstage flavor for plugins by using the `developerHub.flavor` field
29
29
30
-
With this update, you can use the `developerHub.flavor` field to identify whether plugins are running on {product-very-short}, {rhtap-very-short}, or vanilla Backstage, as shown in the following example:
31
-
32
-
.`app-config.yaml` fragment with the `developerhub.flavor` field
33
-
34
-
[source,yaml,subs="+quotes"]
35
-
----
36
-
developerHub:
37
-
flavor: <flavor>
38
-
----
39
-
40
-
`flavor`::
30
+
With this update, you can use the `developerHub.flavor` field to identify whether plugins are running on {product-very-short}, {rhtap-very-short}, or vanilla Backstage, as shown in the following example:
31
+
32
+
.`app-config.yaml` fragment with the `developerhub.flavor` field
33
+
34
+
[source,yaml,subs="+quotes"]
35
+
----
36
+
developerHub:
37
+
flavor: <flavor>
38
+
----
39
+
40
+
`flavor`::
41
41
Identify the flavor of Backstage that is running. Default value: `rhdh`
42
42
43
43
[id="feature-rhidp-4419"]
44
44
== Ability to manage Persistent Volume Claim (PVCs) in {product-very-short} Operator
45
45
46
-
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
47
-
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].
46
+
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
47
+
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].
48
48
49
49
50
+
[id="feature-rhidp-4780"]
51
+
== [Docs] Document per-ConfigMap/Secret configuration of mountPath
52
+
53
+
(Added the link to this document to the Release Notes item which was added on 1.4)
@@ -55,8 +61,8 @@ With this update, you can use {rhbk-brand-name} as an authentication provider. T
55
61
[id="feature-rhidp-4806"]
56
62
== Ability to install third-party plugins in {product-very-short}
57
63
58
-
You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.
59
-
64
+
You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.
65
+
60
66
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html-single/installing_and_viewing_plugins_in_red_hat_developer_hub/index#assembly-install-third-party-plugins-rhdh[Installing third-party plugins in {product}].
0 commit comments