NAT not working on VirutalBox with kubernetes, PC -> [ VM -> haproxy -> MetalLB -> Ingress controller -> Kubernetes web server ]

By -

Im trying to connect to a webserver deployed in kubernetes, from outside of the vm. I've connected the pod to an ingress controller and gave the ingress controller a LoadBalancer IP via MetalLB, then created a forward rule in HAproxy to redirect the traffic to the VM IP, and then created a NAT rule in the VirutalBox configuration.

I can, from inside the VM, curl to either localhost or the NIC ip, and it gives back the deployment response, but from my machine (virtualbox host), if i curl to the NATed rule, it fails.

Here's the configuration:

Nat rule:
  NAME     PROT      HOST IP     HOST PORT    GUEST IP   GUEST PORT 
Rule 1   |  TCP  | 192.168.1.5 |    22    | 10.0.2.15 |     22      | (I use this to ssh to the vm)
Rule 2   |  TCP  | 192.168.1.5 |    80    | 10.0.2.15 |     80      | (This should work for connecting to the web server)

nmcli (or ip addr ): inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic

haproxy cfg:

frontend haproxy_inbound
        bind *:80
        default_backend haproxy_httpd

backend haproxy_httpd
        server test.minikube 172.17.0.5



kubernetes config:
kubectl get ing
NAME                CLASS    HOSTS                                 ADDRESS   PORTS  
wordpress-ingress   <none>   test.minikube                                   80     

kubectl get svc --all-namespaces
NAMESPACE       NAME                        TYPE           CLUSTER-IP       EXTERNAL-IP  PORT(S)                       
kube-system     traefik-ingress-service     LoadBalancer   10.96.170.40     172.17.0.5   80:32547/TCP,8080:32628/TCP   

test (inside the vm)
$ curl 172.17.0.5
Hello!
$ curl 10.0.2.15 
Hello!
$ curl test.minikube
Hello!

test (outside the vm)
curl 192.168.1.5
curl: (52) Empty reply from server
curl http://192.168.1.5
curl: (52) Empty reply from server

ssh root@192.168.1.5 (i can connect through port 22)
Last login: Sun Sep 27 17:11:10 2020 from gateway

what i am missing? im really lost here



from Recent Questions - Stack Overflow https://ift.tt/2GbM6tB
https://ift.tt/eA8V8J

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more