Go to file
Alexey Perevalov 76fa78cfde Fix CNI_COMMAND=VERSION case
In case of VERSION command k8s v1.16 and higher sends
only {"cniVersion": "0.4.0"} to the stdio, but kuryr-cni
expected cni-conf with kuryr_conf field.

Also k8s expects json in the stdio, but logs was also there.
So need to strictly redirect it into stderr in this case.

It's a work around, because maintanable way here is to use
golang's version based on containernetworking library.

Change-Id: I9095ced11f78eb1ae2890883fa6da4df74213480
Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
2019-10-11 14:48:35 +03:00
2019-07-05 11:40:28 -04:00
2019-04-04 12:33:42 +02:00
2016-11-18 10:14:56 +03:00
2018-09-25 12:16:08 +02:00
2019-04-19 19:44:54 +00:00
2018-07-16 15:43:10 +00:00
2019-06-17 12:58:37 +02:00
2019-09-23 15:59:22 +08:00
2019-09-23 15:59:22 +08:00
2018-03-01 14:27:13 +08:00
2019-07-05 11:40:28 -04:00
2017-03-15 12:44:19 +00:00
2018-07-16 15:43:10 +00:00
2019-09-23 15:59:22 +08: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