tamalsaha Expose flags to chart (#1281)
- [x] --bypass-validating-webhook-xray
- [x] --use-kubeapiserver-fqdn-for-aks

Signed-off-by: Tamal Saha <tamal@appscode.com>
Latest commit f7e05c2 Oct 14, 2018



Voyager by AppsCode - Secure HAProxy Ingress Controller for Kubernetes


$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm install appscode/voyager


This chart bootstraps an ingress controller deployment on a Kubernetes cluster using the Helm package manager.


  • Kubernetes 1.8+

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release appscode/voyager

The command deploys Voyager 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

Uninstalling the Chart

To uninstall/delete the my-release:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.


The following tables lists the configurable parameters of the Voyager chart and their default values.

Parameter Description Default
replicaCount Number of operator replicas to create (only 1 is supported) 1
voyager.registry Docker registry used to pull Voyager image appscode
voyager.repository Voyager container image voyager
voyager.tag Voyager container image tag 8.0.1
haproxy.registry Docker registry used to pull HAProxy image appscode
haproxy.repository HAProxy container image haproxy
haproxy.tag HAProxy container image tag 1.8.12-8.0.1-alpine
cleaner.registry Docker registry used to pull Webhook cleaner image appscode
cleaner.repository Webhook cleaner container image kubectl
cleaner.tag Webhook cleaner container image tag v1.11
imagePullSecrets Specify image pull secrets nil (does not add image pull secrets to deployed pods)
imagePullPolicy Image pull policy IfNotPresent
cloudProvider Name of cloud provider nil
cloudConfig Path to cloud config ``
criticalAddon If true, installs Voyager operator as critical addon false
logLevel Log level for operator 3
persistence.enabled Enable mounting cloud config false
persistence.hostPath Host mount path for cloud config /etc/kubernetes
affinity Affinity rules for pod assignment {}
annotations Annotations applied to operator pod(s) {}
nodeSelector Node labels for pod assignment {}
tolerations Tolerations used pod assignment {}
rbac.create If true, create and use RBAC resources true
serviceAccount.create If true, create a new service account true
serviceAccount.name Service account to be used. If not set and serviceAccount.create is true, a name is generated using the fullname template ``
ingressClass Ingress class to watch for. If empty, it handles all ingress ``
templates.cfgmap Name of configmap with custom templates ``
apiserver.groupPriorityMinimum The minimum priority the group should have. 10000
apiserver.versionPriority The ordering of this API inside of the group. 15
apiserver.enableValidatingWebhook Configure apiserver as adission webhooks for Voyager CRDs true
apiserver.ca CA certificate used by main Kubernetes api server not-ca-cert
apiserver.disableStatusSubresource If true, disables status sub resource for crds. Otherwise enables based on Kubernetes version false
apiserver.bypassValidatingWebhookXray If true, bypasses validating webhook xray checks false
apiserver.useKubeapiserverFqdnForAks If true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 true
enableAnalytics Send usage events to Google Analytics true

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example:

$ helm install --name my-release --set image.tag=v0.2.1 appscode/voyager

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example:

$ helm install --name my-release --values values.yaml appscode/voyager


By default the chart will not install the recommended RBAC roles and rolebindings.

You need to have the flag --authorization-mode=RBAC on the api server. See the following document for how to enable RBAC.

To determine if your cluster supports RBAC, run the the following command:

$ kubectl api-versions | grep rbac

If the output contains "beta", you may install the chart with RBAC enabled (see below).

Enable RBAC role/rolebinding creation

To enable the creation of RBAC resources (On clusters with RBAC). Do the following:

$ helm install --name my-release appscode/voyager --set rbac.create=true