kuryr-multi-tenant-support

Registered by liujinxin on 2020-09-11

We need to support use multi-tenant subnets on pod and service .
Note:Although tenant information is not used in k8s, k8s is keenly interested in tenant segregation of the network. If kuryr-cni can support multi-tenant network isolation, it will be a feature that makes kuryr project better than other cni projects.

This requires.
* Support for ns creation of tenant-specific subnetId, sgId by annotation.( (if not specified, use the default subnetId or namespace_subnet in the config file))

* Support for pod creation by annotation specifying tenant subnetId, sgId, fixedIP, Qos.(if not specified, use the configuration in kns)

* Support for service creation by specifying tenant subnetId through annotation. (if not specified, use service_subnet in the config file)

* Adaptation of kuryr_tempest

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
liujinxin
Direction:
Needs approval
Assignee:
liujinxin
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.