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.

Sign up for GitHub

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

Jump to bottom

FloatingIPPoolConf improvement #96

Open

chenchun opened this issue Oct 22, 2020 · 0 comments

Milestone

Contributor

chenchun commented Oct 22, 2020

Currently, configuring multiple pod subnets for the same node subnets is redundant and not clear. e.g.

[{
	"nodeSubnets": ["10.0.0.32/32", "10.0.0.48/32"],
	"ips": ["192.168.0.2~192.168.0.254"],
	"subnet": "192.168.0.0/24",
	"gateway": "192.168.0.1"
}, {
	"nodeSubnets": ["10.0.0.32/32", "10.0.0.48/32"],
	"ips": ["192.168.1.2~192.168.1.254"],
	"vlan": 3,
	"subnet": "192.168.1.0/24",
	"gateway": "192.168.1.1"
}]

I propose adding a FloatingIPPoolConfV2 to rewrite it into

[{
	"nodeSubnets": ["10.0.0.32/32", "10.0.0.48/32"],
	"podSubnets": [{
		"ips": ["192.168.0.2~192.168.0.254"],
		"subnet": "192.168.0.0/24",
		"gateway": "192.168.0.1"
	}, {
		"ips": ["192.168.1.2~192.168.1.254"],
		"vlan": 3,
		"subnet": "192.168.1.0/24",
		"gateway": "192.168.1.1"
	}]
}]

The text was updated successfully, but these errors were encountered:

chenchun added this to the v1.0.7 milestone

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