Installation

    Install Traefik Mesh Helm Chart:

      Supported Installations

      Please be aware that the supported installation method is via Helm, using official releases. If you want to build/install/run Traefik Mesh from source, we may not be able to provide support. Installing from source is intended for development/contributing.

      To build the image locally, run:

      1. make

      You will then be able to use the tagged image as your image in your values.yaml file.

      To deploy the Helm Chart, run:

      KubeDNS support

      1. helm install traefik-mesh traefik-mesh/traefik-mesh --set kubedns=true

      With the kubedns parameter Traefik Mesh will install CoreDNS and patch KubeDNS to use it as a .

      If you use a cluster domain other than cluster.local set it by using the clusterDomain parameter:

      1. helm install traefik-mesh traefik-mesh/traefik-mesh --set clusterDomain=my.custom.domain.com

      Access Control List

      By default, Traefik Mesh does not restrict traffic between pods and services. However, some scenarios require more control over the rules for internal communication. The Access Control List mode (ACL) requires a set of rules to explicitly allow traffic between different resources.

      To enable ACL, install Traefik Mesh in ACL mode by setting the acl Helm Chart option to .

      Traefik Mesh supports the SMI specification which defines a set of custom resources to provide a fine-grained control over instrumentation, routing and access control of east-west communications.

      CRDs

      Traefik Mesh works on Kubernetes environments that conforms to the global Kubernetes specification. That being said, we have had users encounter issues when using variants such as minikube, microk8s, and other development distributions.

      Traefik Mesh runs without issue on most public clouds (AWS, GKE, Azure, DigitalOcean, and more). If you want to run Traefik Mesh in development, we would recommend using , as it is fully conformant. We use k3s in Traefik Mesh’s integration tests, so you can be sure that it works properly.

      If you encounter issues on variants such as minikube or microk8s, please try and reproduce the issue on k3s. If you are unable to reproduce, it may be an issue with the distribution behaving differently than official Kubernetes.

      Verify your installation

      You can check that Traefik Mesh has been installed properly by running the following command:

      Command

      1. kubectl get all -n traefik-mesh

      Expected Output

      2. NAME                                            READY   STATUS    RESTARTS   AGE
      3. pod/traefik-mesh-controller-676fb86b89-pj8ph    1/1     Running   0          11s
      4. pod/traefik-mesh-proxy-w62z5                    1/1     Running   0          11s
      6. NAME                                DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
      7. daemonset.apps/traefik-mesh-proxy   2         2         0       2            0           <none>          29s
      9. NAME                                      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
      10. deployment.apps/traefik-mesh-controller   1         1         1            0           28s
      12. NAME                                                 DESIRED   CURRENT   READY   AGE

      By default, Traefik Mesh is opt-in, meaning you have to use the Traefik Mesh service names to access the mesh, so you can have some services running through the mesh, and some services not.