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

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