Setup Ingress with Traefik

Learn how to route cluster-external HTTP/s requests to cluster-internal services using Traefik.

Before completing the following steps, read the Infrastructure Recommendation page.


We are now shipping Pachyderm with an embedded proxy allowing your cluster to expose one single port externally. This deployment setup is optional.

If you choose to deploy Pachyderm with a Proxy, our new recommended architecture and deployment instructions overwrite the following instructions.

This section provides an example of how to route cluster-external HTTP/HTTPS requests to cluster-internal services (here Pachyderm UI console service and authentication services using the ingress controller Traefik.

Traefik ingress controller on Pachyderm UI’s cluster in one diagram #

Here is a quick high-level view of the various components at play.



The following installation steps are for Informational Purposes ONLY. Please refer to your full Traefik documentation for further installation details and any troubleshooting advice.

Traefik installation and Ingress resource Definition #

  1. Helm install Traefik:

    • Get Repo Info
    helm repo add traefik
    helm repo update
    • Install the Traefik helm chart (helm v3)
    helm install traefik traefik/traefik
    • Run a quick check:
    kubectl get all 

    You should see your Traefik pod, service, deployments.apps, and

    You can now access your Traefik Dashboard at following the port-forward instructions (You can choose to apply your own Ingress resource instead.):

    kubectl port-forward $(kubectl get pods --selector "" --output=name) 9000:9000
  2. Configure the Ingress in the helm chart. You will need to configure any specific annotations your ingress controller requires.

    • my_pachyderm_values.yaml

        enabled: false
        host: "<your_domain_name>"

      For a list of all available annotations, read the Traefik & Kubernetes documentation.

      At a minimum, you will need to specify the host field: match the hostname header of the http request (domain).

      Check the list of all available helm values at your disposal in our reference documentation.

  3. Install Pachyderm and Console using the Helm Chart

    Once you have your networking infrastructure set up, apply a helm values file such as the one specified in the example file below to wire up routing through an Ingress, and set up TLS.

       enabled: true
       host: <DNS-ENTRY-A>
          ## annotations specific to integrate with your ingress-controller
          enabled: true
          secretName: "pach-tls"
          enabled: true
          secretName: "pach-tls"
          enabled: true
          loadBalancerIP: <DNS-ENTRY-B>
       enabled: true
    helm install pachyderm -f my_pachyderm_values.yaml pach/pachyderm

    The deployment of Pachyderm automatically creates the required set of rules.

  4. Check your new rules by running kubectl describe ingress console: s kubectl describe ingress console Name: console Namespace: default Address: Default backend: default-http-backend:80 Rules: Host Path Backends console.localhost / console:console-http ( Annotations: traefik /dex pachd:identity-port ( Annotations: traefik / pachd:oidc-port ( Annotations: traefik Events: <none>

  5. Check the Traefik Dashboard again (, your new set of rules should now be visible.

Browse #

Connect to your Console (Pachyderm UI): https://<external-IP-address-or-domain-name>:443/ (if TLS is enabled) or http://<external-IP-address-or-domain-name>:80/. You are all set!

References #