The below tests were introduced in 4.18, and fixed by OCPBUGS-53249. For a permanent resolution on 4.18 onward, the test framework is supporting the platform type external (flag --provider), requiring to update the test step https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh#L201-L211 (agnostic for OCP version).

To prevent failures in existing supported platform type External jobs on <4.18, we'll need the test framework to support the provider type too.

---> Original bug affecting 4.18+
    The e2e tests[1] are permanent failing in clusters installed with platform type External on CI (installed on providers AWS and vSphere) due missing configuration in the tests (AWS), and vSphere (not supported as we don't use NSX-T).

Those tests need to be skipped to prevent false signals on CI and in the provider auto-validation throughout the VCSP program.

[1] tests failing on platform type External

~~~
[sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s] 
~~~

    4.18

Always

1. install an OpenShift cluster with platform type External on AWS provider with CCM enabled
2. Run the openshift/conformance suite
3. Check the results with tests listed in [1] failing

Tests listed in [1] failing platform type External    

Tests fixed or skipped.