$ helm install --name argo-mydomain chart/Tip: See Your First Tunnel.
Argo Tunnel Ingress Controller provides Kubernetes Ingress via Argo Tunnels. The controller establishes or destroys tunnels by monitoring changes to resources.
Argo Tunnel offers an easy way to expose web servers securely to the internet, without opening up firewall ports and configuring ACLs. Argo Tunnel also ensures requests route through Cloudflare before reaching the web server so you can be sure attack traffic is stopped with Cloudflare’s WAF and Unmetered DDoS mitigation and authenticated with Access if you’ve enabled those features for your account.
To install the chart with the release name argo-mydomain:
$ helm install --name argo-mydomain chart/Tip: See Your First Tunnel.
The command deploys the controller on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Tip: List all releases using
helm list
To uninstall/delete the argo-mydomain deployment:
$ helm delete argo-mydomainThe following table lists the configurable parameters of the chart and their default values.
| Parameter | Description | Default |
|---|---|---|
controller.name |
name of the controller component | controller |
controller.image.repository |
controller container image repository | gcr.io/stackpoint-public/argot |
controller.image.tag |
controller container image tag | 0.5.2 |
controller.image.pullPolicy |
controller container image pull policy | Always |
controller.ingressClass |
name of the ingress class to route through this controller | argo-tunnel |
controller.logLevel |
log-level for this controller | 2 |
controller.replicaCount |
desired number of controller pods | 1 |
loadBalancing.enabled |
if true, replicaCount may be >1, requires load balancing enabled on account |
false |
rbac.create |
if true, create & use RBAC resources |
true |
serviceAccount.create |
if true, create a service account |
true |
serviceAccount.name |
The name of the service account to use. If not set and create is true, a name is generated using the fullname template. |
`` |
A useful trick to debug issues with ingress is to increase the logLevel.
$ helm install chart/ --set controller.logLevel=6