Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

default cni network does not support multi-node #385

Merged

Conversation

silenceshell
Copy link
Contributor

If the network is default cni, I think we cannot access vm's IIP from other computers as the IP is like 172.18.0.0/16.

@silenceshell silenceshell requested a review from twelho as a code owner September 1, 2019 14:34
@chanwit
Copy link
Member

chanwit commented Sep 1, 2019

@silenceshell I think this is not true for a multi-host CNI like Weave Net.
Weave Net, for example, offers IPs in the 10.32.0.0/16 space and accessible across nodes.

@silenceshell
Copy link
Contributor Author

yeah, weave is an-third-party-cni-plugin, and supports multi-node, while the default cni is bridge and not support multi-node.

{
	"cniVersion": "0.4.0",
	"name": "ignite-containerd-bridge",
	"plugins": [
		{
			"type": "bridge",
			"bridge": "cni0",
			"isGateway": true,
			"isDefaultGateway": true,
			"promiscMode": true,
			"ipMasq": true,
			"ipam": {
				"type": "host-local",
				"subnet": "172.18.0.0/16"
			}
		},
		{
			"type": "portmap",
			"capabilities": {
				"portMappings": true
			}
		}
	]
}

@chanwit
Copy link
Member

chanwit commented Sep 1, 2019

oh sorry. I haven't read the whole doc. This LGTM then.

@stealthybox stealthybox merged commit 0693997 into weaveworks:master Sep 3, 2019
@silenceshell silenceshell deleted the default-cni-no-multi-node branch September 3, 2019 23:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants