Merge pull request #8638 from bfallonf/ingress

added ingress support section

Author: Brice Fallon-Freeman

architecture/networking/routes.adoc

@@ -833,3 +833,64 @@ $ oc expose service/<name> --hostname="m.api.openshift.org"
 $ oc expose service/<name> --hostname="kates.net"
 $ oc expose service/<name> --hostname="api.kates.net"
 ----
+
+[[architecture-routes-support-for-ingress]]
+== Support for Kubernetes ingress objects
+
+The Kubernetes ingress object is a configuration object determining how inbound
+connections reach internal services. {product-title} has support for these
+objects, starting in {product-title} version 3.10, using a ingress controller configuration file.
+
+This controller watches ingress objects and creates one or more routes to
+satisfy the conditions of the ingress object. The controller is also responsible
+for keeping the ingress object and generated route objects synchronized. This
+includes giving generated routes permissions on the secrets associated with the
+ingress object. 
+
+For example, an ingress object configured as:
+
+[source, yaml]
+----
+kind: Ingress
+apiVersion: extensions/v1beta1
+metadata:
+  name: test
+spec:
+  rules:
+  - host: test.com
+    http:
+     paths:
+     - path: /test
+       backend:
+        serviceName: test-1
+        servicePort: 80
+----
+
+generates the following route object:
+
+[source, yaml]
+----
+kind: Route
+apiVersion: route.openshift.io/v1
+metadata:
+  name: test-a34th <1>
+  ownerReferences:
+  - apiVersion: extensions/v1beta1
+    kind: Ingress
+    name: test
+    controller: true
+spec:
+  host: test.com
+  path: /test
+  to:
+    name: test-1
+  port:
+     targetPort: 80
+----
+<1> The name is generated by the route objects, with the ingress name as a prefix.
+
+[NOTE]
+====
+In order for a route to be created, an ingress object must have a host,
+service, and path.
+====