Skip to content
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

add support for user networks #20

Closed
naorlivne opened this issue Aug 7, 2017 · 2 comments
Closed

add support for user networks #20

naorlivne opened this issue Aug 7, 2017 · 2 comments

Comments

@naorlivne
Copy link
Member

as mentioned in #19 having user network options might be a good idea to allow inner-pod communication between containers be done with the container hostname DNS resolution.

there are 2 options to go about it I'm still undecided will be better:

  1. ensure a default Nebula user network exists (create it if needed) at worker-manager boot and connect all of the containers managed by nebula to it.
  2. add the option of having users create & attach their own user networks to Nebula apps.

It's really a question of customizability vs sane defaults, thoughts?

@naorlivne
Copy link
Member Author

Also thinking it might be better to deprecate network_mode and to replace it networks as the only method of networking as by default they have the none\host\bridge networks that can do just about everything network_mode can and also allow custom networks as a bonus

@naorlivne
Copy link
Member Author

Main feature added in 1.1.0

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

No branches or pull requests

1 participant