
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
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://git.openstack.org/cgit/openstack/kuryr-kubernetes
- Bugs: https://bugs.launchpad.net/kuryr-kubernetes
- Overview and demo: http://superuser.openstack.org/articles/networking-kubernetes-kuryr
Contribution guidelines
For the process of new feature addition, refer to the Kuryr Policy
Description