You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a question about how to use the sail-operator
Bug Description
Recently, the following PRs in the Istio project introduced the IP_FAMILIES flag for validating dual-stack use cases. This flag can be set to IPv4, IPv6, "IPv4,IPv6", or "IPv6,IPv4", where specifying both families indicates a dual-stack cluster, with the order representing preference.
Currently, Sail Operator's e2e tests validate dual-stack environments, but they do not consider the order of ipFamilies.
Due to the above changes, the automation job that sync's upstream changes into Sail Operator is failing, and we need to fix it.
The text was updated successfully, but these errors were encountered:
This PR sets KIND_IP_FAMILY to align with the IP_FAMILY used in
Sail Operator scripts. Since the order of IP families is not
relevant for Sail Operator e2e tests, we do not require the
IP_FAMILIES variable used upstream.
Fixes: istio-ecosystem#558
Signed-off-by: Sridhar Gaddam <[email protected]>
Is this the right place to submit this?
Bug Description
Recently, the following PRs in the Istio project introduced the IP_FAMILIES flag for validating dual-stack use cases. This flag can be set to IPv4, IPv6, "IPv4,IPv6", or "IPv6,IPv4", where specifying both families indicates a dual-stack cluster, with the order representing preference.
The relevant PRs are:
[Dual-stack] Introduce IP_FAMILIES for integration tests istio/istio#54421
Introduce IP_FAMILIES for integration tests istio/test-infra#5571
rename IP_FAMILY to KIND_IP_FAMILY for better clarity istio/common-files#1135
Currently, Sail Operator's e2e tests validate dual-stack environments, but they do not consider the order of ipFamilies.
Due to the above changes, the automation job that sync's upstream changes into Sail Operator is failing, and we need to fix it.
The text was updated successfully, but these errors were encountered: