Open
Description
What happened:
coredns is in Running state, however the ready container is 0/1; coredns pod log has following error record:
...
Failed to list *v1.Endpoints: Get \"https://10.40.0.2:443/api/v1/endpoints?limit=500\u0026resourceVersion=0\": dial tcp 10.40.0.2:443: connect: no route to host\n","stream":"stderr","time":"2022-02-14T19:07:10.303482004Z"}
Failed to list *v1.Service: Get \"https://10.40.0.2:443/api/v1/services?limit=500\u0026resourceVersion=0\": dial tcp 10.40.0.2:443: connect: no route to host\n","stream":"stderr","time":"2022-02-14T19:07:20.515095501Z"}
What you expected to happen:
coredns able to list resources of TP master
How to reproduce it (as minimally and precisely as possible):
using code of poc-2022-01-30, run kube-up.sh to start 1 TP 1RP 1worker scale-out cluster,
Anything else we need to know?:
10.40.0.2 is the node (physical) IP address of its TP master
Environment:
- Arktos version (use
kubectl version): poc-2022-0130, commit 2b6855 - Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release): - Kernel (e.g.
uname -a): - Install tools: kube-up scale-out 1+1x1
- Network plugin and version (if this is a network-related bug):
- Others: