Support for spaces on Kubernetes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Although it is now possible to deploy workloads on Kubernetes with multiple network interfaces attached (i.e. by using Multus CNI), it is not possible to model such deployments with Juju. This could be addressed by providing support for spaces on Kubernetes.
This feature is important in the OSM context as it will enable the deployments of CNFs (container network functions) with multiple network interfaces attached on Kubernetes. CNFs, as VNFs, are special types of workloads which usually have very demanding requirements with regards to performance and security. For example, certain types of traffic should be attached to certain underlying physical networks for better performance. Or due to regulatory requirements, certain types of traffic should be isolated from other types.
For this can we get specific details as to expected CNI plugins (is multus the only one we're concerned with currently?) that we should test/support and expectations for single containers spanning those and how those workloads would determine things like default gw, interact with the k8s load balancer (e.g. is that part of the space defnintion of a k8s cloud?) and other network primitives?