Go to file
Luis Tomas Bolivar 7061f4abac Make CNI Registry Plugin namespace aware
As with the k8sCNIRegistryPlugin the watching is for the
complete node, instead of per pod and namespace, we need
to make registry information to account for the namespace
where the pod is created to differentiate between different
containers running on the same node, with the same name, but
in a different namespace

Related-Bug: 1731486
Change-Id: I26e1dec6ae613c5316a45f93563c4a015df59441
2018-03-02 16:09:57 +01:00
2018-02-07 15:11:20 +01:00
2017-10-09 15:32:20 +02:00
2016-10-04 21:56:50 +03:00
2016-11-18 10:14:56 +03:00
2016-05-12 09:14:08 +00:00
2018-03-01 14:27:13 +08:00
2018-01-27 17:47:08 +00:00
2017-03-15 12:44:19 +00:00

Team and repository tags

image

Project description

Kubernetes integration with OpenStack networking

The OpenStack Kuryr project enables native Neutron-based networking in Kubernetes. With Kuryr-Kubernetes it's now possible to choose to run both OpenStack VMs and Kubernetes Pods on the same Neutron network if your workloads require it or to use different segments and, for example, route between them.

Contribution guidelines

For the process of new feature addition, refer to the Kuryr Policy

Description
RETIRED, Kubernetes integration with OpenStack networking
Readme 46 MiB