Installing with the Helm Chart¶

Deployment Only

The Traefik Enterprise Helm Chart provides support for deploying and upgrading core components such as the Controllers, Proxies and Plugin Registry, without applying any runtime configuration by default.

Requirements¶

Helm version 3 installed
Kubernetes version 1.13 or greater

Adding the Traefik Enterprise repository¶

Run the following command to add the repository:

helm repo add traefik https://traefik.github.io/charts

Run the following command to update the repository:

helm repo update

Deploy the cluster¶

To deploy Traefik Enterprise in the default Kubernetes namespace:

helm install traefikee traefik/traefikee

Although, it is recommended to deploy Traefik Enterprise in a separate namespace:

helm install traefikee traefik/traefikee --namespace traefikee --create-namespace

The next step is to create the Kubernetes secret that will hold the Traefik Enterprise license key.

kubectl create secret generic $CLUSTERNAME-license --from-literal=license="$TRAEFIKEE_LICENSE" -n traefikee

The command above assumes two environment variables named $CLUSTERNAME and $TRAEFIKEE_LICENSE are already defined.

Setting cluster name

The cluster name can customized with the cluster key on your deployment values file or directly as a flag:

helm install traefikee traefik/traefikee --set "cluster=mycluster" --namespace traefikee --create-namespace

Custom deploy parameters¶

The following command will display all available configuration parameters that can be changed according to the needs.

helm show values traefik/traefikee

The output of the command can be redirected to a file e.g. values.yaml and then modified accordingly and used with the Helm install command.

helm install traefikee traefik/traefikee -f values.yaml

HA Values¶

This chart provides an example of a high-availability set of defaults.

curl -L https://raw.githubusercontent.com/traefik/traefikee-helm-chart/master/traefikee/values-ha.yaml

One can apply it as custom values:

curl -O https://raw.githubusercontent.com/traefik/traefikee-helm-chart/master/traefikee/values-ha.yaml
# Update HA values accordingly to your needs
helm install traefikee traefik/traefikee -f values-ha.yaml

Applying a static configuration¶

After deploying, the cluster will be up and running, with a simple static configuration, set in values:

controller:
[...]
  staticConfig:
#    configMap:
#      name: traefik-config
#      key: "static.yml"
    content: |
      entrypoints:
        web:
          address: ":7000"
        websecure:
          tls: {}
          address: ":7443"
      ping: {}
      providers:
        kubernetesIngress:
          allowEmptyServices: true
        kubernetesCRD:
          allowEmptyServices: true

This configuration allows to run Traefik Enterprise securely, without using a privileged port, with liveness and readyness using /ping.

There are two main approaches for applying a static configuration to the cluster at this point:

by updating the static configuration set with values of Helm Chart
by creating another Kubernetes ConfigMap with its content, outside of the Helm Chart

Creating another Kubernetes ConfigMap¶

Create the config map by executing the following command:

kubectl create configmap --from-file=static.yaml $CLUSTERNAME-static-config -n traefikee

Once the ConfigMap is created, it must be mounted on the controllers with the proxy.staticConfig.configMap and proxy.staticConfig.configMapKey flags:

helm upgrade --install traefikee traefik/traefikee --set "cluster=$CLUSTERNAME,controller.staticConfig.content=null,controller.staticConfig.configMap.name=$CLUSTERNAME-static-config,controller.staticConfig.configMap.key=static.yaml" --namespace traefikee --create-namespace

Reloading the static configuration

Each time the config map is updated Traefik Enterprise will reload the changes automatically.

Next steps¶

Take a look at the Operations guide for instructions on setting up the Traefik Dashboard and API
Deploy a sample application with an Ingress by following this guide