Yossi Boaron d5902e8fed OCP-Router: OCP-Route and Ingress LBaaS handlers
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
2018-06-15 14:47: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-04-10 15:01:09 +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