Updating the OSSM operator triggers a replacement of the istiod and istiocni deployments. However, to utilize the latest proxy image, the user must also redeploy all existing deployments that include the istio-proxy (a necessary step, similar to an Istio version update in IstioCR).

The documentation's "Updating" section details how to update the Istio version by modifying the Istio CR's spec.version (e.g., from 1.27.3 to 1.27.4). However, even when a newer OSSM patch release does not include a different Istio version (e.g., EOL istio stream, like now in the current OSSM 3.0), the component images might contain newer CVE fixes in both their base images and code. Operator updates all component images except proxies. To utilize a newer proxy image in this scenario, the user must manually redeploy all existing deployments that use the proxy.

Can we add a NOTE at the begging of the release note? (e.g. after existing note)

To use the latest available images for proxy, do not forget to restart/rollout all deployments with proxy after the operator update

https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0/html/release_notes/ossm-release-notes
https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.1/html/release_notes/ossm-release-notes 
https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.2/html/release_notes/ossm-release-notes