Installation of Operator with BPF Dataplane Crashes Due to API Server Resolution Failure about operator HOT 3 OPEN

Switching the dnsPolicy to Default appears to be working, the AWS EKS endpoint resolves. Yay! Using the endpoint for the proxy I have running in front of the API doesn't, which is odd. However, the error is that the certificate is signed by an unknown authority, so it's no longer within the scope of this issue.

May be good to note the need to change the dnsPolicy in the docs for enabling BPF.

from operator.

This might just be a helm chart issue which is not in this repository. Could you try manually changing the dns policy for operator and see if one will work? (You should be able to do that by editing the tigera-operator deployment.)
If this is just a helm chart issue, then dnsPolicy might need to be exposed in which case an issue on projectcalico/calico should be created as that is the source of the helm chart.
If it doesn't work to change the dnsPolicy then I'm not sure what solution will be.

from operator.

@shelby-moore as @tmjd says this should be resolved by switching the Tigera Operator dnsPolicy.

If you need something simpler than a manual change I have an alternative Tigera Operator chart that already supports setting hostNetwork & dnsPolicy; although these appear to currently be missing from the documentation they are in values.yaml.

from operator.