Skip to content

Commit 3da5a7a

Browse files
author
Kalyani Desai
committed
SRVCOM-3238-1.33.2-RN: Added two fixed issues in the release notes
1 parent f99cedd commit 3da5a7a

File tree

2 files changed

+18
-1
lines changed

2 files changed

+18
-1
lines changed

about/serverless-release-notes.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
:_content-type: ASSEMBLY
2-
include::_attributes/common-attributes.adoc[]
32
[id="serverless-release-notes"]
43
= Release notes
4+
include::_attributes/common-attributes.adoc[]
55
:context: serverless-release-notes
66

77
toc::[]
@@ -28,6 +28,7 @@ include::modules/serverless-deprecated-removed-features.adoc[leveloffset=+1]
2828

2929
// Release notes included, most to least recent
3030
// OCP + OSD + ROSA
31+
include::modules/serverless-rn-1-33-2.adoc[leveloffset=+1]
3132
include::modules/serverless-rn-1-33-0.adoc[leveloffset=+1]
3233

3334
// OCP + OSD + ROSA

modules/serverless-rn-1-33-2.adoc

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
// Module included in the following assemblies
2+
//
3+
// * about/serverless-release-notes.adoc
4+
5+
:_content-type: REFERENCE
6+
[id="serverless-rn-1-33-2_{context}"]
7+
= Red Hat {ServerlessProductName} 1.33.2
8+
9+
{ServerlessProductName} 1.33.2 is now available. Fixed issues that pertain to {ServerlessProductName} on {ocp-product-title} are included in the following notes:
10+
11+
[id="fixed-issues-1-33-2_{context}"]
12+
== Fixed issues
13+
14+
* Previously, creating Knative installation resources like `KnativeServing` or `KnativeEventing` in a user namespace triggered an infinite reconciliation loop in the {ServerlessOperatorName}. This issue has been resolved by reintroducing an admission webhook that prevents the creation of Knative installation resources in any namespace other than `knative-serving` or `knative-eventing`.
15+
16+
* Previously, post-install batch jobs were removed after a certain period, leaving privileged service accounts unbound. This caused compliance systems to flag the issue. The problem has been resolved by retaining completed jobs, ensuring that service accounts remain bound.

0 commit comments

Comments
 (0)