Skip to content

Conversation

@tedaveryredhat
Copy link

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 23, 2025

@tedaveryredhat: This pull request references OSDOCS-16651 which is a valid jira issue.

In response to this:

Version(s):
4.18

Issue:
https://issues.redhat.com/browse/OSDOCS-16651

Link to docs preview:

Additional information:

4.18.27 MR: https://gitlab.cee.redhat.com/hybrid-platforms/art/ocp-shipment-data/-/merge_requests/192
4.18.27 ART Dashboard: https://art-dash.engineering.redhat.com/dashboard/release/openshift-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 23, 2025
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 23, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 23, 2025

🤖 Thu Oct 23 19:22:39 - Prow CI generated the docs preview:

https://101031--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html

@openshift-ci openshift-ci bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 23, 2025

* Before this update, if the OVN-Kubernetes controller was not processing updates from the Kubernetes API server and configuring the open virtual network (OVN) databases on each node, then the OVN-Controller, which consumed this database, might have connected to the database before the OVN-Kubernetes controller had configured them. As a consequence, the OVN-Controller synced with a stale OVN database, consumed source network address translations (SNATs) that were configured to support the egress IP, and proceeded to the gratuitous address resolution protocol (GARP) for the associated IP even though that IP might have moved to another node. With this release, these GARPs are blocked when the OVN-Kubernetes controller is not processing updates. (link:https://issues.redhat.com/browse/OCPBUGS-62671[OCPBUGS-62671])

* Before this update, the Cluster Version Operator (CVO) in 4.19.9 and 4.18.23 started to require bearer token authentication in metrics requests. As a consequence, HyperShift and Hosted clusters were broken where the metrics scraper currently provides no client authentication. With this release, the CVO does not require client authentication for metrics requests. As a result, access to cluster-version operator metrics is recovered on HyperShift clusters. (link:https://issues.redhat.com/browse/OCPBUGS-62869[OCPBUGS-62869])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.

@openshift-ci
Copy link

openshift-ci bot commented Oct 23, 2025

@tedaveryredhat: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants