Our support for dual-stack aims to mirror upstream Istio's support level. Istio 1.17 brought in initial experimental dual stack support, described here:

https://istio.io/latest/blog/2023/experimental-dual-stack/

A pre-requisite for this epic is a 2.5 build.

We should do a "smoke test" of this feature on a dual-stack cluster to determine if it can be declared developer preview.

"smoke test" = a simple one time manual test to ensure the basics works. This likely means firing up a dual-stack cluster with Cluster bot installing OSSM, enabling the dual-stack feature (via the techPreview field), installing Bookinfo and manually testing that the bookinfo application works as expected.

We do NOT need to incorporate any level of automation around dual-stack testing, and should NOT yet include dual-stack as part of our Jenkins pipelines. We should NOT debug maistra-test-tool failures, as the feature is experimental upstream and may have significant gaps.

If the smoke tests pass, we will declare this feature as "Developer Preview" for Service Mesh 2.5. If the smoke test does not pass - if we are unable to configure dual-stack, Istio throws fatal errors once configured or bookinfo is non-operational, we will declare the feature as "not supported" in 2.5.

Of course, as we have availability, we will look to contribute and support dual-stack development in upstream Istio and Envoy. This epic is scoped to the experimental support of dual-stack in 1.17, which is the equivalent of developer preview in OSSM.

Additional Related Upstream Issues:

https://github.com/istio/istio/issues/40394

Related OSSM Issues:

https://issues.redhat.com/browse/OSSM-331