K
Q

How to expose mongo containers to outside of the overlay network?

11/17/2019

I am running a mongodb replica set as containers in Mesos cluster ( My question also applied to k8s/swarm). The replica set can be initialized using DNS or container IPs. But, both DNS or container IPs can be accessed only in the overlay network of the Mesos cluster. Now, users want to access the mongo replica set from outside the Mesos/K8s cluster, how can they achieve this through an ingress/marathon-lb?

Not to consider HostPort here, because only the ingress/lb nodes are exposed to the public network.

-- Haoyuan Ge
docker
kubernetes
mesos
mongodb

Similar Questions

How could affect my billing if i use docker hub instead of google image registry?
How to deploy spark on Kubeedge?
Kubernetes Ingress routing by service label
What is correct way to configure https to my services (kubernetes, nginx-ingress, letsencrypt, cert-manager)?
On EKS how do I verify I configured a Spot Instance through Terraform
Kubernetes network policy deny-all policy not blocking basic communication
Error converting YAML to JSON: yaml: line 15: did not find expected alphabetic or numeric character
Argo workflow getting auto deleted after successful completion
Istio rating limit with redisquota not taken into account
Why kubectl returns pods with 'Terminating' status when I query for just running pods?
ArgoCD Private Repo Declarative Approach
K8s/Helm - how to mount volume based on value attribute?

1 Answer

11/18/2019

Ingress controller is using HTTP and it does not support TCP. MongoDB require regular TCP/IP socket.

There are two other ways to achieve that:

  • You can useNodePort or Loadbalancer service. If this runs on cloud then you can use loadbalancer, otherwise use NodePort. More information about services can be found here.
  • Alternatively you could use nginx ingress controller

Both solution are explained in this Mongodb tutorial

-- acid_fuji
Source: StackOverflow