Allow setting dnsPolicy for Kubernetes executor
Description
My use case includes multiple Docker images that need to communicate. I need to pass environmental configs into them, so I am unable to run them as services. I cannot access localhost
from within one container to access the other. If I could use Docker networks, I could get name-based access between containers. But this conflicts with the ClusterFirst
DNS policy in the pod. If I were able to change the DNS policy for the pod (e.g. .dnsPolicy
: None
, .dnsConfig.nameservers
: [8.8.8.8]
), I think kube-dns
would allow fall-back to the Docker DNS shim.
Proposal
Allow the user to control the dnsPolicy and dnsConfig settings for the per-job runner pods spawned by the runner/executor.
Links to related issues and merge requests / references
This is a start, but it needs the None
option and the dnsConfig
settings.
:/
I'd be happy to do this, but it's completely beyond me.