76fa78cfdea39795d927d6f639bd6224d9c2dc04

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>
Team and repository tags
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/kuryr-kubernetes/latest
- Source: https://opendev.org/openstack/kuryr-kubernetes
- Bugs: https://bugs.launchpad.net/kuryr-kubernetes
- Overview and demo: https://superuser.openstack.org/articles/networking-kubernetes-kuryr
- Release notes: https://docs.openstack.org/releasenotes/kuryr-kubernetes/
Contribution guidelines
For the process of new feature addition, refer to the Kuryr Policy
Description