# Help setting up with k0s

**URL:** https://community.traefik.io/t/help-setting-up-with-k0s/20745
**Category:** Traefik v2
**Tags:** kubernetes-ingress
**Created:** [December 12, 2023, 10:58am UTC](https://community.traefik.io/t/help-setting-up-with-k0s/20745 "2023-12-12T10:58:15Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![R-in-Tokyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/r-in-tokyo/32/7941_2.png) [@R-in-Tokyo](https://community.traefik.io/u/R-in-Tokyo)
#### Post date: [December 12, 2023, 10:58am UTC](https://community.traefik.io/t/help-setting-up-with-k0s/20745/1 "2023-12-12T10:58:15Z")

</div>

Following the Traefik and k3s documentation had example files that didn’t go as smoothly.

I have a multi node k0s setup and tried the this Traefik example deployment via helm charts extension.

But with that yaml config posted on k0s Getting Started I don’t have an external IP.

> **[Traefik Ingress Controller - Documentation](https://docs.k0sproject.io/v1.28.4+k0s.0/examples/traefik-ingress/)**
>
> Documentation for k0s, the Zero friction Kubernetes distribution.

```auto
extensions:
  helm:
    repositories:
    - name: traefik
      url: https://traefik.github.io/charts
    - name: bitnami
      url: https://charts.bitnami.com/bitnami
    charts:
    - name: traefik
      chartname: traefik/traefik
      version: "20.5.3"
      namespace: default
    - name: metallb
      chartname: bitnami/metallb
      version: "2.5.4"
      namespace: default
      values: |
        configInline:
          address-pools:
          - name: generic-cluster-pool
            protocol: layer2
            addresses:
            - 192.168.0.5-192.168.0.10

```