d5902e8fed
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
16 lines
559 B
YAML
16 lines
559 B
YAML
---
|
|
features:
|
|
- |
|
|
An OpenShift route is a way to expose a service by giving it an
|
|
externally-reachable hostname like www.example.com.
|
|
A defined route and the endpoints identified by its service can be
|
|
consumed by a router to provide named connectivity that allows external
|
|
clients to reach your applications.
|
|
Each route consists of a route name , target service details.
|
|
To enable it the following handlers should be added :
|
|
|
|
.. code-block:: ini
|
|
|
|
[kubernetes]
|
|
enabled_handlers=vif,lb,lbaasspec,ingresslb,ocproute
|