github.com/projectcontour/contour@v1.28.2/site/content/docs/v1.2.0/configuration.md (about)

     1  # Contour Configuration
     2  
     3  A configuration file can be passed to the `contour serve` command which specified additional properties that Contour should use when starting up.
     4  This file is passed to Contour via a ConfigMap which is mounted as a volume to the Contour pod.
     5  
     6  Following is an example ConfigMap with configuration file included: 
     7  
     8  ```yaml
     9  apiVersion: v1
    10  kind: ConfigMap
    11  metadata:
    12    name: contour
    13    namespace: projectcontour
    14  data:
    15    contour.yaml: |
    16      # should contour expect to be running inside a k8s cluster
    17      # incluster: true
    18      #
    19      # path to kubeconfig (if not running inside a k8s cluster)
    20      # kubeconfig: /path/to/.kube/config
    21      #
    22      # disable ingressroute permitInsecure field
    23      # disablePermitInsecure: false
    24      tls:
    25        # minimum TLS version that Contour will negotiate
    26        # minimumProtocolVersion: "1.1"
    27      # The following config shows the defaults for the leader election.
    28      # leaderelection:
    29        # configmap-name: leader-elect
    30        # configmap-namespace: projectcontour
    31  ```
    32  
    33  _Note:_ The default example `contour` includes this [file][1] for easy deployment of Contour.
    34  
    35  [1]: {{< param github_url >}}/tree/{{page.version}}/examples/contour/01-contour-config.yaml