Argo Tunnel Ingress Controls
February 1, 2019 ยท View on GitHub
Ingress Annotations
kubernetes.io/ingress.class: the Ingress class that should interpret and serve the Ingress- defaults to
argo-tunnel - override with the command-line option
--ingressClass=
- defaults to
argo.cloudflare.com/compression-quality: Use cross-stream compression instead HTTP compression.- defaults to
"0" - quality:
- 0 - off
- 1 - low
- 2 - medium
- 3 - high
- defaults to
argo.cloudflare.com/ha-connections: the number of high-availability connections to establish- defaults to
"4"
- defaults to
argo.cloudflare.com/heartbeat-count: minimum number of unacknowledged heartbeats to send before closing the connection- defaults to
"5"
- defaults to
argo.cloudflare.com/heartbeat-interval: minimum idle time before sending a heartbeat- defaults to
"5s"
- defaults to
argo.cloudflare.com/lb-pool: attach a Cloudflare loadbalancer for high-availability- load-balancing must be enabled for the Cloudflare account
- allows balancing traffic across clusters
- required if replicas > 1
argo.cloudflare.com/no-chunked-encoding: disables chunked transfer encoding; useful if you are running a WSGI server- defaults to
"false"
- defaults to
argo.cloudflare.com/retries: maximum number of retries for connection/protocol errors- defaults to
"3"
- defaults to
argo.cloudflare.com/tag: custom tags used to identify the ingress tunnels- defaults to
"" - format
KEY1=VALUE1,KEY2=VALUE2,KEY3=VALUE3 - the system limits tags to 32 unique custom tags
- defaults to
Command-Line Options
--default-origin-secret: the default certificate used to establish tunnels- any tunnel that does not specify a secret will use this default.
--origin-secret-config: the default certificate used for specific hosts- any matching host that does not specify a secret will use this default.
- see origin-secret-config
--transport-log-enable: enable tunnel transport logging--v: set the controller log level- defaults to
"3"
- defaults to
--watch-namespace: restrict resource watches to a namespace