Update documentation examples

README.md

@@ -75,7 +75,8 @@ spec:
     # Email address used for ACME registration
     email: ""
     # Name of a secret used to store the ACME account private key
-    privateKey: letsencrypt-staging
+    privateKeySecretRef:
+      name: letsencrypt-staging
     # ACME dns-01 provider configurations
     dns-01:
       # Here we define a list of DNS-01 providers that can solve DNS challenges
@@ -85,7 +86,7 @@ spec:
       - name: prod-dns
         clouddns:
           # A secretKeyRef to a the google cloud json service account
-          serviceAccount:
+          serviceAccountSecretRef:
             name: clouddns-service-account
             key: service-account.json
           # The project in which to update the DNS zone
@@ -127,7 +128,8 @@ spec:
   # The name of the Kubernetes secret resource to store the signed TLS keypair
   secretName: example-com
   # The Issuer to use for this certificate
-  issuer: letsencrypt-staging
+  issuerRef:
+    name: letsencrypt-staging
   # A list of domains to include on the TLS certificate
   domains:
   - example.com

docs/api-types/issuer/README.md

@@ -17,7 +17,8 @@ spec:
     # Email address used for ACME registration
     email: user@example.com
     # Name of a secret used to store the ACME account private key
-    privateKey: letsncrypt-prod
+    privateKeySecretRef:
+      name: letsncrypt-prod
 ```
 
 This is the simplest of ACME issuers - it specifies no DNS-01 challenge

docs/api-types/issuer/spec.md

@@ -21,7 +21,8 @@ spec:
     server: https://acme-v01.api.letsencrypt.org/directory
     email: user@example.com
     # Name of a secret used to store the ACME account private key
-    privateKey: letsncrypt-prod
+    privateKeySecretRef:
+      name: letsncrypt-prod
 ```
 
 ## ACME configuration
@@ -57,7 +58,8 @@ spec:
   acme:
     email: user@example.com
     server: https://acme-staging.api.letsencrypt.org/directory
-    privateKey: example-issuer-account-key
+    privateKeySecretRef:
+      name: example-issuer-account-key
 ```
 
 ### ACME issuer DNS provider configuration
@@ -80,7 +82,7 @@ spec:
       providers:
       - name: prod-clouddns
         clouddns:
-          serviceAccount:
+          serviceAccountSecretRef:
             name: prod-clouddns-svc-acct-secret
             key: service-account.json
 ```
@@ -99,7 +101,7 @@ a listing of them all, with an example block of configuration:
 
 ```yaml
 clouddns:
-  serviceAccount:
+  serviceAccountSecretRef:
     name: prod-clouddns-svc-acct-secret
     key: service-account.json
 ```
@@ -110,7 +112,7 @@ clouddns:
 route53:
   accessKeyID: AKIAIOSFODNN7EXAMPLE
   region: eu-west-1
-  secretAccessKey:
+  secretAccessKeySecretRef:
     name: prod-route53-credentials-secret
     key: secret-access-key
 ```
@@ -120,7 +122,7 @@ route53:
 ```yaml
 cloudflare:
   email: my-cloudflare-acc@example.com
-  secretAccessKey:
+  apiKeySecretRef:
     name: cloudflare-api-key-secret
     key: api-key
 ```

docs/examples/acme-cert.yaml

@@ -6,7 +6,8 @@ metadata:
   name: cm-http-nginx-k8s-group
 spec:
   secretName: cm-http-nginx-k8s-group
-  issuer: letsencrypt-staging
+  issuerRef:
+    name: letsencrypt-staging
   domains:
   - cm-http-nginx.k8s.group
   - cm-http-nginx2.k8s.group

docs/examples/acme-issuer.yaml

@@ -2,13 +2,31 @@ apiVersion: certmanager.k8s.io/v1alpha1
 kind: Issuer
 metadata:
   name: letsencrypt-prod
-  namespace: skeleton-review
 spec:
   acme:
     # The ACME server URL
     server: https://acme-v01.api.letsencrypt.org/directory
     # Email address used for ACME registration
-    email: james+workshops@jetstack.io
+    email: user@example.com
     # Name of a secret used to store the ACME account private key
-    privateKey: letsncrypt-prod
+    privateKeySecretRef:
+      name: letsncrypt-prod
     # ACME dns-01 provider configurations
+    dns-01:
+      # Here we define a list of DNS-01 providers that can solve DNS challenges
+      providers:
+      - name: prod-dns
+        clouddns:
+          # A secretKeyRef to a the google cloud json service account
+          serviceAccountSecretRef:
+            name: clouddns-service-account
+            key: service-account.json
+          # The project in which to update the DNS zone
+          project: gcloud-prod-project
+      - name: cf-dns
+        cloudflare:
+          email: user@example.com
+          # A secretKeyRef to a the google cloud json service account
+          apiKeySecretRef:
+            name: cloudflare-api-key
+            key: api-key.txt

docs/examples/ca-cert.yaml

@@ -6,6 +6,10 @@ metadata:
   name: test-ca-crt
 spec:
   secretName: test-ca-crt
-  issuer: ca-issuer
+  issuerRef:
+    name: ca-issuer
+    # We can reference ClusterIssuers by changing the kind here.
+    # The default value is Issuer (i.e. a locally namespaced Issuer)
+    kind: Issuer
   domains:
   - cert-manager.k8s.io

docs/examples/ca-issuer.yaml

@@ -4,5 +4,4 @@ metadata:
   name: ca-issuer
 spec:
   ca:
-    secretRef:
-      name: ca-key-pair
+    secretName: ca-key-pair