Original: * Previously, there was an upstream rebase that revealed a dependency related to a higher version of Golang than necessary for {product-title} 4.13. With this release, the upstream rebase is reverted, the dependency is removed, and the issue has been resolved. (link:https://issues.redhat.com/browse/OCPBUGS-32920[*OCPBUGS-32920*])
* Previously, if traffic was forwarded to terminating endpoints that were not functioning, communications problems occurred unless the readiness probes on these endpoints were configured to quickly flag the endpoints as not serving. This occurred because the endpoint selection for services partially implemented KEP-1669 `ProxyTerminatingEndpoints` traffic to services inside the {product-title} cluster. As a result, this traffic was forwarded to all endpoints that were either ready, such as `ready=true`, `serving=true`, `terminating=false`, or terminating and serving, such as `ready=false`, `serving=true`, `terminating=true`. This caused communication issues when traffic was forwarded to terminating endpoints and the readiness probes on these endpoints were not configured to quickly flag the endpoints as not serving, `serving=false`, when they were no longer functional. With this release, the endpoints selection logic now fully implements KEP-1669 `ProxyTerminatingEndpoints` for any given service so that all ready endpoints are selected. If no ready endpoints are found, functional terminating and serving endpoints are used. (link:https://issues.redhat.com/browse/OCPBUGS-33421[*OCPBUGS-33421*])
* Previously, the {vmw-short} Problem Detector Operator did not have HTTP and HTTPS proxies configured for it. This resulted in invalid cluster configuration error messages because of connection issues between the Operator and the {vmw-full} vCenter server. With this release, the {vmw-short} Problem Detector Operator uses the same HTTP and HTTPS proxies as other {product-title} cluster Operators so that the {vmw-short} Problem Detector Operator can connect to the {vmw-full} vCenter. (link:https://issues.redhat.com/browse/OCPBUGS-33468[*OCPBUGS-33468*])
* Previously, if you need the *Form* view in the {product-title} web console to remove an alternate service from a `Route` resource, the alternate service remained in the cluster. With this release, if you delete an alternate service in this way, the alternate service is fully removed from the cluster. (link:https://issues.redhat.com/browse/OCPBUGS-33650[*OCPBUGS-33650*])
* Previously, if you configured an {product-title} cluster with a high number of internal services or user-managed load balancer IP addresses, you experienced a delayed startup time for the OVN-Kubernetes service. This delay occurred when the OVN-Kubernetes service attempted to install `iptables` rules on a node. With this release, the OVN-Kubernetes service can process a large number of services in a few seconds. Additionally, you can access a new log to view the status of installing `iptables` rules on a node. (link:https://issues.redhat.com/browse/OCPBUGS-33730[*OCPBUGS-33730*])
* Previously, the installation program did not remove the tag category from vSphere when it deleted a cluster. With this release, the issue has been resolved. (link:https://issues.redhat.com/browse/OCPBUGS-33732[*OCPBUGS-33732*])
* Previously, the *Topology* view in the {product-title} web console did not show the visual connector between a virtual machine (VM) node and other non-VM components. With this release, the visual connector shows interaction activity of a component.  (link:https://issues.redhat.com/browse/OCPBUGS-33749[*OCPBUGS-33749*])
Revised: * Previously, the *Topology* view in the {product-title} web console did not show the visual connector between a virtual machine (VM) node and other non-VM components. With this release, the visual connector shows interaction activity of a component. (link:https://issues.redhat.com/browse/OCPBUGS-33749[OCPBUGS-33749])