To finish off MVP2, we should publish a short blog post that updates our progress. This will not need to be as long as the developer preview release post, but it should include:

• An updated on the operator development (name changes, location, configuration, architecture, etc)
• Discuss importance of modularity and why we are taking this approach.
• An update on new features that have been tested with the operator:
  • Gateway usage (Gateway Injection, Gateway API)
  • Monitoring integraitons (Prometheus, OpenShift monitoring)
  • Kiali integrations
  • Distributed Tracing
  • Istioctl (if complete)
• An update on productization work behind the scenes:
  • Istio integration tests on Openshift.
• Highlight community contributions to improve Istio on OpenShift.
• How can users prepare for OSSM3?
  • Adopt Gateway Injection for the creation of management of Gateways
  • Move to using OpenShift monitoring user-work load monitoring, and external Jaeger, Kiali CRDs
  • Disable IoR and re-implement routes explicitely using OCP route APIs.
  • Move to cluster-wide mode if you only have a single tenant.
• An update on what's next for MVP3 and the path to Technology Preview
• Somewhere in the blog - reiterate the the operator is still Developer Preview

Related issue: OSSM2 vs 3 differences: https://issues.redhat.com/browse/OSSM-4835

Draft of the post: https://docs.google.com/document/d/1biSYdsG8UvVPSwX8Z_mZeRcwXdF3dwbxlaynlw4F528/edit