github.com/projectcontour/contour@v1.28.2/site/content/docs/1.26/troubleshooting/envoy-admin-interface.md (about)

     1  # Accessing the Envoy Administration Interface
     2  
     3  Getting access to the Envoy [administration interface][1] can be useful for diagnosing issues with routing or cluster health.
     4  However, Contour doesn't expose the entire Envoy Administration interface since that interface contains many options, such as shutting down Envoy or draining traffic.
     5  To prohibit this behavior, Contour only exposes the read-only options from the admin interface which still allows for debugging Envoy, but without the options mentioned previously. 
     6  
     7  Those endpoints are:
     8    - /certs
     9    - /clusters
    10    - /listeners
    11    - /config_dump
    12    - /memory
    13    - /ready
    14    - /runtime
    15    - /server_info
    16    - /stats
    17    - /stats/prometheus
    18    - /stats/recentlookups
    19  
    20  The Envoy administration interface is bound by default to `http://127.0.0.1:9001`.
    21  To access it from your workstation use `kubectl port-forward` like so:
    22  
    23  ```sh
    24  # Get one of the pods that matches the Envoy daemonset
    25  ENVOY_POD=$(kubectl -n projectcontour get pod -l app=envoy -o name | head -1)
    26  # Do the port forward to that pod
    27  kubectl -n projectcontour port-forward $ENVOY_POD 9001
    28  ```
    29  
    30  Then navigate to `http://127.0.0.1:9001/` to access the administration interface for the Envoy container running on that pod.
    31  
    32  [1]: https://www.envoyproxy.io/docs/envoy/latest/operations/admin