Kuryr is adding support for a new subnet driver that enables to have a different subnet for each namespace. As it provides this functionality by relying on K8s CRDs, a few modifications are needed to provide the option of enabling the new driver (and namespace handler) and create the required CRD.
To ensure isolation between different namespaces, it is not only needed to configure the kuryr namespace subnet driver but also the namespace security group driver, including the creation of a couple of extra security groups to ensure default namespace can access and be accessed by any pod.
*** Bug 1614216 has been marked as a duplicate of this bug. ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days