Skip to content

Commit 9a463a6

Browse files
authored
Merge pull request #100803 from jeana-redhat/Fix-bug-text
reverting a wording change
2 parents 3c8aca4 + 2814ecf commit 9a463a6

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

release_notes/ocp-4-20-release-notes.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1543,7 +1543,7 @@ With this release, kubelet no longer reports resources for terminated pods, whic
15431543

15441544
* Before this update, the `admissionregistration.k8s.io/v1beta1` API was served incorrectly in {product-title} version 4.17, despite being intended for deprecation and removal. This led to dependency issues for users. With this release, the deprecated API filter is registered for a phased removal, and requires administrative acknowledgment for upgrades. As a result, users do not encounter deprecated API errors in {product-title} version 4.20, and the system stability is improved. (link:https://issues.redhat.com/browse/OCPBUGS-55465[OCPBUGS-55465])
15451545

1546-
* Before this update, the certificate rotation controller copied and rewrote all of their changes, and caused excessive event spamming. As a consequence, users experienced excessive event spamming and potential etcd overload. With this release, the certificate rotation controller conflict is resolved, and reduces excessive event spamming. As a result, excessive event spamming in the certificate rotation controller is resolved, reduces the load on etcd, and improves the system stability.(link:https://issues.redhat.com/browse/OCPBUGS-55217[OCPBUGS-55217])
1546+
* Before this update, the certificate rotation controller copied and rewrote all of their changes, and caused excessive event spamming. As a consequence, users experienced excessive event spamming and potential etcd overload. With this release, the certificate rotation controller conflict is resolved, and reduces excessive event spamming. As a result, excessive event spamming in the certificate rotation controller is resolved, reduces the load on etcd, and improves the system stability.(link:https://issues.redhat.com/browse/OCPBUGS-55217[OCPBUGS-55217])
15471547

15481548
* Before this update, user secrets were logged in audit logs after enabling `WriteRequestBodies` profile settings. As a consequence, sensitive data was visible in the audit log. With this release, the `MachineConfig` object is removed from the audit log response, and prevents user secrets from being logged. As a result, secrets and credentials do not appear in audit logs. (link:https://issues.redhat.com/browse/OCPBUGS-52466[OCPBUGS-52466])
15491549

@@ -1602,7 +1602,10 @@ As a result, compute machine sets successfully transition from the Cluster API t
16021602
With this release, the CRD documents the default value.
16031603
(link:https://issues.redhat.com/browse/OCPBUGS-61314[OCPBUGS-61314])
16041604

1605-
* Before this update, it was possible to specify the use of the `CapacityReservationsOnly` capacity reservation behavior and `SpotInstances` in the same machine template. As a consequence, machines with these two incompatible settings were created. With this release, validation of machine templates ensures that these two incompatible settings are not set at this time. As a result, machines with these two incompatible settings cannot be created. (link:https://issues.redhat.com/browse/OCPBUGS-60943[OCPBUGS-60943])
1605+
* Before this update, it was possible to specify the use of the `CapacityReservationsOnly` capacity reservation behavior and Spot Instances in the same machine template.
1606+
As a consequence, machines with these two incompatible settings were created.
1607+
With this release, validation of machine templates ensures that these two incompatible settings are not used in the same machine template.
1608+
As a result, machines with these two incompatible settings cannot be created. (link:https://issues.redhat.com/browse/OCPBUGS-60943[OCPBUGS-60943])
16061609

16071610
* Before this update, on clusters that support migrating Machine API resources to Cluster API resources, deleting a nonauthoritative machine did not delete the corresponding authoritative machine.
16081611
As a consequence, orphaned machines that should have been cleaned up remained on the cluster and could cause a resource leak.

0 commit comments

Comments
 (0)