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

Do not rely on default docker network 172.17.0.1 #80

Open
Gerrit91 opened this issue Nov 12, 2021 · 3 comments
Open

Do not rely on default docker network 172.17.0.1 #80

Gerrit91 opened this issue Nov 12, 2021 · 3 comments
Assignees

Comments

@Gerrit91
Copy link
Contributor

No description provided.

@Gerrit91 Gerrit91 changed the title Do not rely on default docker-compose network 172.17.0.1 Do not rely on default docker network 172.17.0.1 Nov 15, 2021
@Gerrit91
Copy link
Contributor Author

I don't know if it makes much sense, but maybe we can put the kind cluster into the same docker network. This would enable the leaf switches to directly to the API components and we can maybe get rid off these parts: https://github.com/metal-stack/mini-lab/blob/master/deploy_partition.yaml#L37-L45

@GrigoriyMikhalkin
Copy link
Contributor

GrigoriyMikhalkin commented Nov 17, 2021

I don't know if it makes much sense, but maybe we can put the kind cluster into the same docker network

In that case that would make sense to run kind as a part of containerlab. Otherwise setting with up can be quite dirty) I would create an additional task to research that.

@GrigoriyMikhalkin
Copy link
Contributor

ref: srl-labs/containerlab#689

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

No branches or pull requests

2 participants