Certificate resolvers.

Co-authored-by: Julien Salleyron <julien.salleyron@gmail.com>
Co-authored-by: Jean-Baptiste Doumenjou <jb.doumenjou@gmail.com>

docs/content/user-guides/crd-acme/03-deployments.yml

@@ -33,16 +33,13 @@ spec:
             - --entrypoints.web.Address=:8000
             - --entrypoints.websecure.Address=:4443
             - --providers.kubernetescrd
-            - --acme
-            - --acme.acmelogging
-            - --acme.tlschallenge
-            - --acme.onhostrule
-            - --acme.email=foo@you.com
-            - --acme.entrypoint=websecure
-            - --acme.storage=acme.json
+            - --certificatesresolvers.default.acme.tlschallenge
+            - --certificatesresolvers.default.acme.email=foo@you.com
+            - --certificatesresolvers.default.acme.entrypoint=websecure
+            - --certificatesresolvers.default.acme.storage=acme.json
             # Please note that this is the staging Let's Encrypt server.
             # Once you get things working, you should remove that whole line altogether.
-            - --acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory
+            - --certificatesresolvers.default.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory
           ports:
             - name: web
               containerPort: 8000

docs/content/user-guides/crd-acme/04-ingressroutes.yml

@@ -26,5 +26,5 @@ spec:
     services:
     - name: whoami
       port: 80
-  # Please note the use of an empty TLS object to enable TLS with Let's Encrypt.
-  tls: {}
+  tls:
+    certResolver: default