Address DiscoverySelectors conflict

[PetrMc]

…suecomment-2083122552

Issue #, if available:

Description of changes:

Added "DiscoverySelectors"

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[elamaran11]

@PetrMc Thankyou for such a quick turnaround. We did a revert so your changes from last week is missing in the PR. Please sync your fork and then push the changes.

[PetrMc]

sorry missed it. Should be good to go now.

[elamaran11]

Thankyou @PetrMc We will validate this soon!

[elamaran11]

@PetrMc Could you make this change?

[PetrMc]

@elamaran11 @zirain - the requested change is applied, please let me know if anything else is needed.

[elamaran11]

@elamaran11 @zirain - the requested change is applied, please let me know if anything else is needed.

Thankyou @PetrMc

[mikemcd3912]

Thank you @PetrMc for the quick updates on this! Everything is working as expected and both PR's are co-existing on the cluster with that new edit applied. LGTM

EKSA:

• VMware (K8s 1.28, Bottlerocket 1.15): Pods deploy and reach a ready state, tester completes successfully on first attempt
• Outposts (K8s 1.27, Amazon Linux 2): Pods deploy and reach a ready state, tester completes successfully on first attempt
• Baremetal (K8s 1.27, Ubuntu 20.04.6 LTS): Pods deploy and reach a ready state, tester completes successfully on first attempt

EKS:

• EKS (K8s 1.28, ARM Bottlerocket 1.19): Pods deploy and reach a ready state, tester completes successfully on first attempt
• EKS (K8s 1.28, ARM Amazon Linux 2): Pods deploy and reach a ready state, tester completes successfully on first attempt
• EKS (K8s 1.28, x86 Amazon Linux 2): Pods deploy and reach a ready state, tester completes successfully on first attempt
• EKS (K8s 1.28, x86 Bottlerocket): Pods deploy and reach a ready state, tester completes successfully on first attempt

[elamaran11]

LGTM

[elamaran11]

Looks like your deployment istiod-1-18-3-solo is failing.
Specifically, it looks like these pods are failing:

• Pod: istiod-1-18-3-solo-5f996795d8-czvmd.

---

[PetrMc]

@elamaran11 / @mikemcd3912 is there any action that are required on my end?

[elamaran11]

@PetrMc Thankyou so much for fast action on this and thankyou so much for following back. We are good with this now. We now have both istio based meshes working fine on our EKS and EKS-A clusters. Please check with your team and send us an email or slack if you are interested to do a joint blog on this when you also have the paid product submitted as a PR. Looking forward for your submission of Paid product as a PR and also looking forward to working with you more.