File tree 1 file changed +8
-3
lines changed
1 file changed +8
-3
lines changed Original file line number Diff line number Diff line change @@ -62,6 +62,11 @@ When the cert-manager has been installed, deploy the helm chart on your machine
62
62
export DOMAIN=acme.mydomain.com # replace with your domain
63
63
helm install -n cert-manager godaddy-webhook ./deploy/charts/godaddy-webhook --set groupName=$DOMAIN
64
64
```
65
+
66
+ The ` groupName ` refers to a prior nonexistant Kubernetes API Group, under which custom resources are created.
67
+ The name itself has no connection to the domain names for which certificates are issued, and using the default of
68
+ ` acme.mycompany.com ` is fine.
69
+
65
70
** NOTE** : The kubernetes resources used to install the Webhook should be deployed within the same namespace as the cert-manager.
66
71
67
72
- To change one of the values, create a ` my-values.yml ` file or set the value(s) using helm's ` --set ` argument:
@@ -122,7 +127,7 @@ kubectl apply -f secret.yml -n <NAMESPACE>
122
127
123
128
### ClusterIssuer
124
129
125
- - Create a ` ClusterIssuer ` resource to specify the address of the ACME staging or production server to access.
130
+ - Create a ` ClusterIssuer ` resource to specify the address of the ACME staging or production server to access.
126
131
Add the DNS01 Solver Config that this webhook will use to communicate with the API of the Godaddy Server in order to create
127
132
or delete an ACME Challenge TXT record that the DNS Provider will accept/refuse if the domain name exists.
128
133
@@ -144,8 +149,8 @@ spec:
144
149
name : letsencrypt-<ENV> # staging or production
145
150
solvers :
146
151
- selector :
147
- dnsNames :
148
- - ' *. example.com'
152
+ dnsZones :
153
+ - ' example.com'
149
154
dns01 :
150
155
webhook :
151
156
config :
You can’t perform that action at this time.
0 commit comments