Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Important: Red Hat OpenShift Service Mesh Containers for 2.4.0), and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:3644

To clarify, we are not changing the default enablement for 2.4, but are documenting this feature as deprecated.

rh-ee-yannliu just wanted to follow-up on this now that I'm working on the 2.4 release notes. The last time we chatted we were thinking we might announce IOR as deprecated in the release notes. Just wanted to see what's been learned since then and determine if there is a doc action. Thanks!

Finished implementation, but still fixing up integration test. The test is passed locally but keep failing on the github job.

rh-ee-yannliu and mluksa@redhat.com what are our initial thoughts on the doc impact for this? Presumably we want to announce deprecation in the release notes and describe the basic functional change - basically that IOR is now disabled by default. I assume we want a small code snippet to show how to set it to enabled for customers who want to continue using IOR.

What about the workflow when upgrading from 2.3 to 2.4. Will anything break?

The section of the doc called Differences between Service Mesh and Istio briefly discusses Routes for Istio Gateways and mentions IOR.

Does anything need to be updated - particularly in the section for automatic routes?
https://docs.openshift.com/container-platform/4.11/service_mesh/v2x/ossm-traffic-manage.html#ossm-auto-route_traffic-management