anchor.diff:  // * ingress/configure-ingress-operator.adoc
   
   [id="nw-ingress-controller-configuration-parameters_{context}"]
  -= Ingress controller configuration parameters
  += Ingress Controller configuration parameters
   
   The `ingresscontrollers.operator.openshift.io` resource offers the following
   configuration parameters.
  
positive.code: 
  * The value is published to individual Route statuses so that users know where to target external DNS records.
  
  The `domain` value must be unique among all Ingress controllers and cannot be updated.
  
  If empty, the default value is `ingress.config.openshift.io/cluster` `.spec.domain`.
  
  
negative.code: 
  For request headers, these adjustments are applied only for routes that have the `haproxy.router.openshift.io/h1-adjust-case=true` annotation. For response headers, these adjustments are applied to all HTTP responses. If this field is empty, no request headers are adjusted.
  
  |`tuningOptions`
  |`tuningOptions` specifies options for tuning the performance of Ingress Controller pods.
  
  * `headerBufferBytes` specifies how much memory is reserved, in bytes, for Ingress Controller connection sessions. This value must be at least `16384` if HTTP/2 is enabled for the Ingress Controller. If not set, the default value is `32768` bytes. Setting this field not recommended because `headerBufferBytes` values that are too small can break the Ingress Controller, and `headerBufferBytes` values that are too large could cause the Ingress Controller to use significantly more memory than necessary.
  
  * `headerBufferMaxRewriteBytes` specifies how much memory should be reserved, in bytes, from `headerBufferBytes` for HTTP header rewriting and appending for Ingress Controller connection sessions. The minimum value for `headerBufferMaxRewriteBytes` is `4096`. `headerBufferBytes` must be greater than `headerBufferMaxRewriteBytes` for incoming HTTP requests. If not set, the default value is `8192` bytes. Setting this field not recommended because `headerBufferMaxRewriteBytes` values that are too small can break the Ingress Controller and `headerBufferMaxRewriteBytes` values that are too large could cause the Ingress Controller to use significantly more memory than necessary.
  
  * `threadCount` specifies the number of threads to create per HAProxy process. Creating more threads allows each Ingress Controller pod to handle more connections, at the cost of more system resources being used. HAProxy
  supports up to `64` threads. If this field is empty, the Ingress Controller uses the default value of `4` threads. The default value can change in future releases. Setting this field is not recommended because increasing the number of HAProxy threads allows Ingress Controller pods to use more CPU time under load, and prevent other pods from receiving the CPU resources they need to perform. Reducing the number of threads can cause the Ingress Controller to perform poorly.
  
  |===
  
  
  