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
* chore: release notes for 1.3.4
Signed-off-by: Nick Boldt <[email protected]>
chore: release notes for 1.3.4
Signed-off-by: Nick Boldt <[email protected]>
* regen release notes
Signed-off-by: Nick Boldt <[email protected]>
* generate node/go CVE list
Signed-off-by: Nick Boldt <[email protected]>
* formatting tweaks + enable one of the 4 RPM CVEs until the other 3 are ready
Signed-off-by: Nick Boldt <[email protected]>
* Update modules/release-notes/list-fixed-security-issues-in-product-1.3.4.txt
* Update modules/release-notes/list-fixed-security-issues-in-product-1.3.4.txt
* Update modules/release-notes/list-fixed-security-issues-in-product-1.3.4.txt
* update RN with more fixed rpm and node/go CVEs; add missing RN item for https://issues.redhat.com/browse/RHIDP-5477 bug fix too
Signed-off-by: Nick Boldt <[email protected]>
* regen from jira using ./modules/release-notes/single-source-release-notes.py script
Signed-off-by: Nick Boldt <[email protected]>
* regen known-issue-rhidp-5342 using ./modules/release-notes/single-source-release-notes.py
Signed-off-by: Nick Boldt <[email protected]>
* apply Lindsey's feedback in JIRA and regenerate
Signed-off-by: Nick Boldt <[email protected]>
---------
Signed-off-by: Nick Boldt <[email protected]>
CVE-2024-34156, encoding/gob: golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-breaking-changes.adoc
+64-62Lines changed: 64 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,93 +7,95 @@ This section lists breaking changes in {product} {product-version}.
7
7
[id="removed-functionality-rhidp-3048"]
8
8
== The 'dynamic-plugins' config map is named dynamically
9
9
10
-
Before this update, the dynamic-plugins config map name was hardcoded.
11
-
Therefore, it was not possible to install two {product} helm charts in the same namespace.
12
-
13
-
With this update, the dynamic-plugins config map is named dynamically based on the deployment name similar to how all other components names are generated.
14
-
When upgrading from a previous chart you might need to manually update that section of your `values.yaml` file to pull in the correct config map.
15
-
10
+
Before this update, the dynamic-plugins ConfigMap name was hardcoded.
11
+
12
+
Therefore, it was not possible to install two {product} Helm charts in the same namespace.
13
+
14
+
With this update, the dynamic-plugins ConfigMap is named dynamically based on the deployment name. This naming method is similar to the way that all other component names are generated.
15
+
16
+
When upgrading from a previous chart you might need to manually update that section of your `values.yaml` file to pull in the correct ConfigMap.
== Signing in without user in the software catalog is now disabled by default
22
24
23
-
By default, it is now required for the user entity to exist in the software catalog to allow sign in.
24
-
This is required for production ready deployments since identities need to exist and originate from a trusted source (i.e. the Identity Provider) in order for security controls such as RBAC and Audit logging to be effective.
25
-
To bypass this, enable the `dangerouslySignInWithoutUserInCatalog` configuration that allows sign in without the user being in the catalog.
25
+
By default, it is now required for the user entity to exist in the software catalog to allow sign in.
26
+
This is required for production ready deployments since identities need to exist and originate from a trusted source (i.e. the Identity Provider) in order for security controls such as RBAC and Audit logging to be effective.
27
+
To bypass this, enable the `dangerouslySignInWithoutUserInCatalog` configuration that allows sign in without the user being in the catalog.
26
28
Enabling this option is dangerous as it might allow unauthorized users to gain access.
With this update, all plugins included under the link:https://access.redhat.com/support/offerings/techpreview[Technology Preview scope of support], whether from {company-name} or the community, are disabled by default.
51
-
52
-
.Procedure
53
-
* If your workload requires these plugins, enable them in your custom resource or configmap using `disabled: false`.
54
-
37
+
Before this update, some {company-name} and Community Technology Preview (TP) plugins and actions were enabled by default:
38
+
39
+
.Technology Preview plugins
40
+
* @backstage-community/plugin-catalog-backend-module-scaffolder-relation-processor (changing in RHIDP-3643)
With this update, all plugins included under the link:https://access.redhat.com/support/offerings/techpreview[Technology Preview scope of support], whether from {company-name} or the community, are disabled by default.
53
+
54
+
.Procedure
55
+
* If your workload requires these plugins, enable them in your custom resource or ConfigMap using `disabled: false`.
56
+
55
57
//See https://github.com/redhat-developer/red-hat-developer-hub/blob/main/dynamic-plugins.default.yaml for examples.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-deprecated-functionalities.adoc
+46-47Lines changed: 46 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,56 +7,55 @@ This section lists deprecated functionalities in {product} {product-version}.
7
7
[id="deprecated-functionality-rhidp-1138"]
8
8
== `spec.application.image`, `spec.application.replicas` and `spec.application.imagePullSecrets` fields are deprecated
9
9
10
-
`spec.application.image`, `spec.application.replicas` and `spec.application.imagePullSecrets` fields are deprecated in `v1alpha2` in favour of `spec.deployment`.
11
-
12
-
Procedure:
13
-
14
-
To update your {product-short} Operation configuration:
15
-
16
-
. Remove the `spec.application.image`, `spec.application.replicas` and `spec.application.imagePullSecrets` fields from the Operator configuration:
17
-
+
18
-
[source,yaml]
19
-
----
20
-
spec:
21
-
application:
22
-
replicas: 2 # <1>
23
-
imagePullSecrets: # <2>
24
-
- my-secret-name
25
-
image: quay.io/my/my-rhdh:latest # <3>
26
-
----
27
-
<1> Replica count.
28
-
<2> Array of image pull secrets names.
29
-
<3> Image name.
30
-
31
-
32
-
. Replace the removed fields by new `spec.deployment` fields, such as:
33
-
+
34
-
[source,yaml]
35
-
----
36
-
spec:
37
-
deployment:
38
-
patch:
39
-
spec:
40
-
replicas: 2 # <1>
41
-
imagePullSecrets: # <2>
42
-
- name: my-secret-name
43
-
template:
44
-
metadata:
45
-
labels:
46
-
my: true
47
-
spec:
48
-
containers:
49
-
- name: backstage-backend
50
-
image: quay.io/my/my-rhdh:latest # <3>
51
-
----
52
-
<1> Replica count.
53
-
<2> Array of image pull secrets names.
54
-
<3> Image name.
55
-
10
+
`spec.application.image`, `spec.application.replicas` and `spec.application.imagePullSecrets` fields are deprecated in `v1alpha2` in favour of `spec.deployment`.
11
+
12
+
.Procedure
13
+
To update your {product-short} Operation configuration:
14
+
15
+
. Remove the `spec.application.image`, `spec.application.replicas` and `spec.application.imagePullSecrets` fields from the Operator configuration. For example:
16
+
+
17
+
[source,yaml]
18
+
----
19
+
spec:
20
+
application:
21
+
replicas: 2 # <1>
22
+
imagePullSecrets: # <2>
23
+
- my-secret-name
24
+
image: quay.io/my/my-rhdh:latest # <3>
25
+
----
26
+
<1> Replica count.
27
+
<2> Array of image pull secrets names.
28
+
<3> Image name.
29
+
30
+
31
+
. Replace the removed fields with new `spec.deployment` fields. For example:
0 commit comments