ACME+KubernetesIngress Migration to Traefik V2

Traefik Traefik v2
,
1

I have the following v1 config for acme and Ingress. With this I was able to access https://dash.mydomain.com with a valid lets encrypt cert

# acme toml
[acme]
  email = "my.email.com"
  storage = "my.json"
  caServer = "caserver-for-le"
  entryPoint = "https"
  [acme.dnsChallenge]
    provider = "route53"
  [[acme.domains]]
    main = "*.mydomain.com"
    sans = ["mydomain.com"]
---
# Ingress Definition
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: dash-ingress
  namespace: kube-system
  annotations:
    kubernetes.io/ingress.class: traefik
spec:
  rules:
  - host: dash.mydomain.com
    http:
      paths:
      - path: /
        backend:
          serviceName: dash-service
          servicePort: 443

With v2, the certificatesResolvers.default.acme does not support specifying domains as part of static toml configuration. How do I use the existing Ingress (without migrating to CRD) and still get a valid let's encrypt certificate

2

Unless I'm missing something, you cannot. You need to specify the resolvers (and the domains) with each router, and the way to do it is via IngressRoutes. The v2 Ingresses as I understand do not even use labels as v1 used, so there is no way of fine tuning them.

The documentation encourage to favour IngressRoutes over Ingresses.

If a memeber of traefik team could chime in please - is there anything we are overlooking?