This engineering issue seems to be a change in how we implement CNI in OSSM 2.3, so it's appropriate to mention in the Release Notes and in the Upgrade Considerations topic for 2.3.

Issue includes: "the new behavior and how to verify this change is documented"