148.42 /* default/spiffy:http has no endpoints */ tcp dpt : 8081 reject - with icmp - port - unreachable 159.92 /* default/elasticsearch: has no endpoints */ tcp dpt : 9200 reject - with icmp - port - unreachable 0.0 / 0 /* kubernetes firewall for dropping marked packets */ mark match 0x8000 / 0x8000 ![]() ![]() 0.0 / 0 /* kubernetes service portals */Ĭhain DOCKER - ISOLATION ( 1 references ) 0.0 / 0 ctstate RELATED, ESTABLISHEDĪCCEPT all - 0.0. 0.0 / 0 udp dpt : 68ĭOCKER - ISOLATION all - 0.0. Is there something misconfigured in the networking model? Should I be using an overlay network? If I deploy my pods with shared host network, I get connection to elastic, but I can only share one pod per host, otherwise they - dev1 - master :~ $ sudo iptables - n - L Independent of which VNET this VM might sit on. However the pods/containers which run on these nodes, and are assigned to their own subnets (ex: 10.244.0.0/24, 10.244.1.0/24), cannot connect to the elasticsearch nodes/VMs or to VM outside of the nodes subnet for that matter. Inside the VNET2 kuberenetes nodes run kubernetes pods (which have a containerized api, that needs a connection to the elasticsearch cluster). VNET1 has an elasticsearch cluster, hosted on subnet 10.66.1.0/24 and VNET2 has a kubernetes cluster hosted on 10.55.1.0/24 (which is provisioned by kubernetes-anywhere). ![]() We have a VNET1 (ex: 10.66.0.0/16) and a VNET2 (ex: 10.55.0.0/16), within each of the VNETs we have a gateway and we connect both VNETs using these gateways and VPN connections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |