89a8bd08b5
Initial implementation of kuryr-daemon was only adding new pods to the in-memory registry and not deleting them. While the amount of data is tiny, it will accumulate over time and in practice be a memory leak. We should aim to prevent that, especially taking into account most recent efforts to base health checks on memory usage. This commit makes kuryr-daemon react to pod deletions with removals of pods from the in-memory registry. Change-Id: I45babc325b7a727d6a973717f6653a40503ad991 Closes-Bug: 1750394
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