New deployment on Kubernetes just results in 503's

Traefik Traefik v2 (latest)
1

Hi

Im trying to get traefik v2 working in a kubernetes environment.

Ive deployed all the CRD's successfully.
my traefik deployment contains this:

    spec:
      serviceAccountName: traefik2-ingress-controller
      containers:
        - name: traefik2
          image: traefik:v2.1
          args:
            - --api.dashboard
            - --api.insecure
            - --accesslog
            - --entrypoints.web.Address=:80
            - --entrypoints.websecure.Address=:4443
            - --providers.kubernetescrd
            - --providers.kubernetesingress
            - --metrics.prometheus
          ports:
            - name: web
              containerPort: 80
            - name: websecure
              containerPort: 4443
            - name: admin
              containerPort: 8080

my dashboard service - which is the first thing I want ot get going is this:

---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: traefik-dashboard
spec:
  routes:
  - match: Host(`mydomain.here.com`)
    kind: Rule
    services:
    - name: api@internal
      kind: TraefikService
---

curling to this, results in:

< HTTP/1.1 503 Service Unavailable: Back-end server is at capacity
HTTP/1.1 503 Service Unavailable: Back-end server is at capacity

The logs for the container contains alot of this:

time="2020-02-03T03:37:07Z" level=error msg="Error while reading basic auth middleware: auth secret must be set" providerName=kubernetescrd middlewareName=default-auth