kube-static-egress-ip icon indicating copy to clipboard operation
kube-static-egress-ip copied to clipboard

unable to ping destination IP

Open jazzsir opened this issue 5 years ago • 1 comments

I am trying to apply nirmata/kube-static-egress-ip to my cluster on bare-metal. but, I can't access(ping) destination IP(172.30.1.103)

my env is below

  • CNI: weave
$ kubectl get node -o wide
NAME      STATUS    ROLES     AGE       VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION CONTAINER-RUNTIME
dev      Ready     master    190d      v1.11.2   172.30.1.100   <none>  Ubuntu 18.04.1 LTS   4.15.0-33-generic   docker://18.6.1
node01    Ready     <none>    190d      v1.11.2   172.30.1.102   <none>  Ubuntu 18.04.1 LTS   4.15.0-46-generic   docker://18.6.1
apiVersion: staticegressips.nirmata.io/v1alpha1
kind: StaticEgressIP
metadata:
  name: test
spec:
  rules:
  - egressip: 172.30.1.102
    service-name: nginx-with-curl
    cidr: 172.30.1.103/24
$ kubectl get pod -nkube-system -o wide
NAME                          READY     STATUS    RESTARTS   AGE       IP             NODE      NOMINATED NODE
coredns-78fcdf6894-d9nc7      1/1       Running   19         190d      10.32.0.47     dev       <none>
coredns-78fcdf6894-fgq55      1/1       Running   19         190d      10.32.0.45     dev       <none>
egressip-controller-njdmb     1/1       Running   7          23h       172.30.1.102   node01    <none>
egressip-controller-vnmjq     1/1       Running   4          23h       172.30.1.100   dev       <none>
etcd-dev                      1/1       Running   19         190d      172.30.1.100   dev       <none>
kube-apiserver-dev            1/1       Running   19         190d      172.30.1.100   dev       <none>
kube-controller-manager-dev   1/1       Running   19         190d      172.30.1.100   dev       <none>
kube-proxy-wdkgw              1/1       Running   20         190d      172.30.1.100   dev       <none>
kube-proxy-xfft6              1/1       Running   14         190d      172.30.1.102   node01    <none>
kube-scheduler-dev            1/1       Running   20         190d      172.30.1.100   dev       <none>
weave-net-8q82g               2/2       Running   41         190d      172.30.1.102   node01    <none>
weave-net-92nxn               2/2       Running   59         190d      172.30.1.100   dev       <none>

jazzsir avatar Mar 14 '19 06:03 jazzsir

@jazzsir thanks for reporting the issue.

As noted in https://github.com/nirmata/kube-static-egress-ip#status currently it works with only direct routing (i.e calico, flannel host-gw, kube-router etc) and pending issue to make it work with overlay networks #13

I am working on next release which will fix the issue. Will update once there is release.

murali-reddy avatar Mar 14 '19 08:03 murali-reddy