You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by camer314 <ca...@towerswatson.com> on 2019/12/17 06:37:09 UTC
Getting UnknownHostException: kubernetes.default.svc.cluster.local
when using hostNetwork
Hello,
I have setup a Kubernetes environment with auto discovery and the nodes are
able to find one another no problem. I did have several issues along the way
which this forum has helped resolve, including some modifications to YAML
that differ from those from the Ignite docs.
However, now when I set /hostNetwork: true/, I am getting
*UnknownHostException: kubernetes.default.svc.cluster.local*
If i remove the hostNetwork condition then it all starts to work again.
What is so different about this setting? I thought this was something
standard in Kubernetes/Docker?
This is the fragment of my deployment that is relevant:
spec:
#hostNetwork: true
serviceAccountName: ignite
containers:
# Custom Ignite pod name.
- name: ignite-node
image: apacheignite/ignite:2.4.0
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Getting UnknownHostException:
kubernetes.default.svc.cluster.local when using hostNetwork
Posted by camer314 <ca...@towerswatson.com>.
I found a solution to this which you might want to update your documentation
with.
The answer is to add a dnsPolicy for the pod along with hostNetwork, as per
below:
spec:
hostNetwork: true
dnsPolicy: ClusterFirstWithHostNet
serviceAccountName: ignite
containers:
# Custom Ignite pod name.
- name: ignite-node
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/