![Yossi Boaron](/assets/img/avatar_default.png)
This is the third patch of the Ingress Controller capability. This patch implements OCP-Route and Ingress LBaaS handlers. Those handlers should retrieve the L7 LB details from the Ingress controller and update L7 policy/rules and pool/members upon changes in OCP-route and k8S-endpoint resources. Please follow the instructions below to verify OCP-Router functionality: https://docs.google.com/document/d/1c3mfBToBbWlwFcw3S8fr7pQZb5_YZqFYdlG1HqaQPkQ/edit?usp=sharing Implements: blueprint openshift-router-support Change-Id: Ibfb6cda6dde9613ad31859d38235be031ade0639
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