OSDOCS-14578: adds ingress control options to MicroShift

Author: ShaunaDiaz

modules/microshift-config-yaml-custom.adoc

@@ -5,6 +5,7 @@
 :_mod-docs-content-type: CONCEPT
 [id="microshift-yaml-custom_{context}"]
 = Using custom settings
+
 To create custom configurations, make a copy of the `config.yaml.default` file that is provided in the `/etc/microshift/` directory, renaming it `config.yaml`. Keep this file in the `/etc/microshift/` directory, and then you can change supported settings that are expected to override the defaults before starting or restarting {microshift-short}.
 
 [IMPORTANT]

modules/microshift-default-settings.adoc

@@ -42,6 +42,30 @@ dns:
 etcd:
   memoryLimitMB: 0
 ingress:
+  accessLogging:
+    destination:
+      container:
+        maxLength: 1024
+      syslog:
+        address: ""
+        facility: ""
+        maxLength: 1024
+        port: 0
+      type: ""
+    httpCaptureCookies:
+      - matchType: ""
+        maxLength: 0
+        name: ""
+        namePrefix: ""
+    httpCaptureHeaders:
+      request:
+        - maxLength: 0
+          name: ""
+      response:
+        - maxLength: 0
+          name: ""
+    httpLogFormat: ""
+    status: Disabled
   certificateSecret: router-certs-default
   clientTLS:
     allowedSubjectPatterns:
@@ -54,6 +78,8 @@ ingress:
     mimeTypes:
       - ""
   httpEmptyRequestsPolicy: Respond
+  httpErrorCodePages:
+      name: ""
   listenAddress:
     - ""
   logEmptyRequests: Log

modules/microshift-ingress-controller-config.adoc

@@ -91,7 +91,79 @@ ingress:
 |Parameter |Description
 
 |`ingress`
-|The `ingress` section of the {microshift-short} `config.yaml` file defines the configurable parameters for the implemented portions of the {OCP} Ingress Control Operator. All parameters in the rest of this table are subsections in the `ingress` section of the `config.yaml`.
+|The `ingress` section of the {microshift-short} `config.yaml` file defines the configurable parameters for the implemented portions of the {OCP} Ingress Control Operator. All of the following parameters in this table are subsections in the `ingress` section of the `config.yaml`.
+
+|`accessLogging`
+|
+
+|`accessLogging.destination`
+|
+
+|`accessLogging.destination.container`
+|
+
+|`accessLogging.destination.container.maxLength`
+|Default value is 1024.
+
+|`accessLogging.destination.syslog`
+|
+
+|`accessLogging.destination.syslog.address`
+|
+
+|`accessLogging.destination.syslog.facility`
+|
+
+|`accessLogging.destination.syslog.maxLength`
+|Default value is 1024.
+
+|`accessLogging.destination.syslog.port`
+|Default value is 0.
+
+|`accessLogging.destination.type`
+|Default value is 0.
+
+|`httpCaptureCookies`
+|
+
+|`httpCaptureCookiesmatchType`
+|
+
+|`httpCaptureCookiesmaxLength`
+|
+
+|`httpCaptureCookiesname`
+|
+
+|`httpCaptureCookiesnamePrefix`
+|
+
+|`httpCaptureHeaders`
+|
+
+|`httpCaptureHeaders.request`
+|
+
+|`httpCaptureHeaders.request.maxLength`
+|
+
+|`httpCaptureHeaders.request.name`
+|
+
+|`httpCaptureHeaders.response`
+|
+
+|`httpCaptureHeaders.responsemaxLength`
+|
+
+|`httpCaptureHeaders.responsename`
+|
+
+|`httpLogFormat`
+|
+
+|`status`
+|Default value is `Disabled`.
 
 |`certificateSecret`
 |A reference to a `kubernetes.io/tls` type of secret that contains the default certificate that is served by the {microshift-short} ingress controller. When routes do not specify their own certificate, the `certificateSecret` parameter is used. All secrets used must contain `tls.key` key file contents and `tls.crt` certificate file contents.