Darragh Fitzmaurice

/label peer-review-in-progress

Hi @sbeskin-redhat . I agree with Max. The commits need to be squashed, non-intended files should be reverted, and the merge conflict(s) need to be addressed.

/remove-label peer-review-in-progress

/remove-label peer-review-needed /label peer-review-in-progress

Hi @sbeskin-redhat . This PR should target 4.17 also?

Please update the following to state "4.16+". Thank you! 

``` //Update with relevant advisory information [id="ocp-4-20-0-ga_{context}"] === RHSA-202X:XXXXX - {product-title} {product-version}.0 image release, bug fix, and security update advisory Issued: DD MMM YYYY {product-title} release {product-version}.0, which includes security...

I seee some other 4.19 references that will need to be changed to 4.20 or something more generic and transferable: ``` [id="ocp-telco-ran-4-19-known-issues_{context}"] [id="ocp-telco-core-4-19-known-issues_{context}"] ```

``` // TODO: Update with the relevant information closer to release. {product-title} (link:https://access.redhat.com/errata/RHSA-202X:XXXX[RHSA-202X:XXXXX]) is now available. This release uses link:https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.32.md[Kubernetes 1.32] with CRI-O runtime. New features, changes, and known issues...

Might be worth doing now: Comment in the "Even-numbered release lifecycle verbiage (Comment in for even-numbered releases)" section and comment out the "Odd-numbered release lifecycle verbiage (Comment in for odd-numbered...