New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to access pods' ip:port directly from outside world ? #1025

tuxknight opened this Issue Jul 31, 2018 · 0 comments


None yet
1 participant

tuxknight commented Jul 31, 2018

Expected Behavior

While migrating dubbo providers to k8s cluster, dubbo consumers need to access dubbo service (pod's ip:port) in the outside world.

Current Behavior

Couldn't access pods' ip:port directly from outside world.

Possible Solution

Ops add static route rule on gateway devices or hosts. cons: this solution will need manually configuration when adding new nodes(subnet) to cluster.

May be it's a good idea to run an agent(maybe flanneld could do this) on outside hosts to maintain route table automatically.

Any suggestions on this scenario?

Your Environment

  • Flannel version: v0.10.0
  • Backend used (e.g. vxlan or udp): vxlan
  • Etcd version: 3.3.6
  • Kubernetes version (if used): v1.10.4
  • Operating System and version: CentOS Linux release 7.5.1804 (Core)

@tuxknight tuxknight changed the title from How to access pods' ip:port directly from outside word ? to How to access pods' ip:port directly from outside world ? Jul 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment