Michał Dulko 8b7d695d43 Fetch CONTAINERID from Docker API in kuryr-cni
In Kuryr CNI container's entrypoint we were talking to K8s API to get
the current container's CONTAINERID. This worked fine in most cases, but
in more busy environments the value may be not saved into the K8s API
yet and we end up with "null" as CONTAINERID. This obviously breaks
kuryr-cni script that's being injected onto the host.

Instead of implementing retries on "null" this commit uses another
approach and fetches CONTAINERID from Docker API.

Closes-Bug: 1777133

Change-Id: If0bbd55c4dc03077132b140a9a12cf6bd0f0cd03
2018-06-21 21:39:48 +00:00
2018-06-15 11:35:07 +00:00
2017-10-09 15:32:20 +02:00
2018-04-26 09:38:28 +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-06-21 13:59:22 +02:00
2018-03-01 14:27:13 +08:00
2017-03-15 12:44:19 +00:00
2018-06-04 02:13:43 +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