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

Feature: Create network inside namespace #99

Closed
leon3s opened this issue Jan 26, 2023 · 4 comments
Closed

Feature: Create network inside namespace #99

leon3s opened this issue Jan 26, 2023 · 4 comments
Labels
question Further information is requested

Comments

@leon3s
Copy link
Member

leon3s commented Jan 26, 2023

By default when creating a namespace it will create an associated network and all cargo created will use this network.
End-User may want to create other custom network ?

A command like :

nanocl namespace global network create my-network

or

nanocl network create --namespace global my-network

could be implemented. With associated list remove and inspect methods.

This can improove container network isolation.

@leon3s leon3s added enhancement New feature or request good first issue Good for newcomers question Further information is requested labels Jan 26, 2023
@leon3s leon3s changed the title Create network inside namespace Feature: Create network inside namespace Apr 3, 2023
@hnidoaht-101
Copy link

Can I have this plz?

@leon3s leon3s removed the good first issue Good for newcomers label Apr 22, 2023
@leon3s
Copy link
Member Author

leon3s commented Apr 22, 2023

It's more a feature suggestion and open to discussion because it adds complexity and I'm not aware of the difficulty of managing this feature when we have more compatibility for multi node.
I am thinking of using VXLAN for internal communication of containers and virtual machines but i never did it before so.

You can investigate if you want for this you need 2 virtual machines in the same network with docker installed. After you play with the docker network command to create VXLAN between your machine then start 1 container on each machine and try to ping them to have an overview then you can show me how you did setup that i'll be really interested as we will need to replicate it automatically when we add new nodes in the cluster.

@leon3s
Copy link
Member Author

leon3s commented Apr 22, 2023

You can probably do tests with 2 docker in docker setup aswell

@hnidoaht-101
Copy link

It's more a feature suggestion and open to discussion because it adds complexity and I'm not aware of the difficulty of managing this feature when we have more compatibility for multi node. I am thinking of using VXLAN for internal communication of containers and virtual machines but i never did it before so.

You can investigate if you want for this you need 2 virtual machines in the same network with docker installed. After you play with the docker network command to create VXLAN between your machine then start 1 container on each machine and try to ping them to have an overview then you can show me how you did setup that i'll be really interested as we will need to replicate it automatically when we add new nodes in the cluster.

err, I seem to have underestimated this feature, it sounds more complicated than I thought. This is also the first time I heard about VXLAN. I may need to study a bit before practice. Then show you what I have.

@leon3s leon3s removed the enhancement New feature or request label Jun 18, 2023
@leon3s leon3s closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Done
Development

No branches or pull requests

2 participants