Support dnsPolicy and dnsConfigs for operator and webhook in Helm chart.

Question

Support dnsPolicy and dnsConfigs for operator and webhook in Helm chart.

Closed this issue 3 months ago · 5 comments

Hello. I'm trying to use the spark-on-k8s-operator using a different dnsConfig and dnsPolicy due to some restrictions and limitations of k8s cluster that I'm using.

Something like this in values.yaml of helm chart:

dnsConfig:
          nameservers:
          - XXX.XX.X.XXX
dnsPolicy: ClusterFirstWithHostNet

This is necessary because, in my case, if I don't set dnsPolicy: ClusterFirstWithHostNet for the pods in my cluster, it's not solving the dns kubernetes.default.svc used to initialize the webhook. The image below shows the error if I don't set dnsPolicy: ClusterFirstWithHostNet (it happens for both init-webhook and clean-up-webhook)

I need to use the webhook activated in order to some customizations in SparkApplication take effect (like also, configure dnsConfig and dnsPolicy) for driver and executors, otherwise, it will not take effect.

Thanks!

Answer 1 · 2024-04-02T12:33:23.000Z

I'm having the same issue, any updates on this?

Answer 2 · 2024-04-08T23:51:21.000Z

Hi @leticiasss. In my case, the k8s cluster network was fixed and it started to work ( the webhook ). I think one possible workaround for it is to generate the yaml mafinests files from the helm chart, edit the manifests network configs and deploy it manually.

Answer 3 · 2024-04-12T14:21:50.000Z

Hi @messerzen. Thank you for updated. Initially the installation unsuccessful, but did it again, then worked as expected.

Answer 4 · 2024-07-24T20:10:11.000Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Answer 5 · 2024-08-14T00:23:28.000Z

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.