https://doc.traefik.io/traefik-enterprise/installing/kubernetes/gitops/ 

Installing with the GitOps endpoint GitOps practices are a set of workflows and practices that make Git the source of truth for infrastructure configuration management.

Kubernetes only

For now, Traefik Enterprise can be only be installed using GitOps practices on Kubernetes.

Installation To install Traefik Enterprise without the teectl CLI, an HTTP request can be made to generate the required installation manifests, which can then be applied directly to a Kubernetes cluster.

First, your Traefik Enterprise license needs to be specified in a Kubernetes Secret, in the namespace in which you plan to install Traefik Enteprise.

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

As a convenience, a sample declarative file that can be used with kubectl apply has been provided below:

apiVersion: v1 kind: Namespace metadata: name: traefikee namespace: traefikee

apiVersion: v1 kind: Secret type: Opaque metadata: name: default-license namespace: traefikee stringData: license: myLicenseString

The next step is to create a ConfigMap containing your Traefik Enterprise static configuration. Traefik Enterprise will watch this configuration and automatically update all of its proxies whenever the ConfigMap's data is edited.

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

As a convenience, a sample declarative file that can be used with kubectl apply has been provided below:

apiVersion: v1 kind: ConfigMap metadata: namespace: traefikee name: default-static-config data: static.yaml: | entryPoints: http: address: ":80" https: address: ":443"

Now that your license has been applied and your static configuration is in a ConfigMap, you can query the installer service to generate an installation manifest, which you should review and make any changes that are needed:

Applying the installation manifest curl "https://install.enterprise.traefik.io/v2.10 " --output manifest.yaml

Once you have reviewed the manifest, the next step is to apply it using kubectl:

kubectl apply -f manifest.yaml The installation service supports multiple options to customize your installation (namespace, cluster name, etc.).

Custom Installation Parameters

Here are the options that can be specified using query parameters to customize the generated install manifest:

• cluster string (default: default) : The cluster name
• namespace string (default: traefikee) : The namespace in which to install
• clusterdomain string (default: cluster.local) : The cluster domain (required for service mesh)
• controllers integer (default: 1) : The number of controllers
• proxies integer (default: 2) : The number of proxies
• mesh boolean (default: false) : Enable service mesh
• kubedns boolean (default: false) : The cluster has KubeDNS installed
• withoutcrds boolean (default: false) : Do not output the CRD part of the manifest
• withoutresources boolean (default: false) : Do not output the Resources part of the manifest
• staticconfig string (default: static.yaml) : The name of the static configuration file in the ConfigMap

The following command gets an installation manifest that has service mesh enabled, for a cluster that uses KubeDNS, and will install a cluster named staging in the traefikee-staging namespace:

Example: kubectl apply -f "https://install.enterprise.traefik.io/v2.10?cluster=staging&namespace=traefikee-staging&mesh&kubedns "