I was following this tutorial: https://www.youtube.com/watch?v=APnXlMiKBWg&list=WL&index=30&t=0s
everything works until the cert thing, the presenter was mentioning that the order of executing matters (apply the certs first THEN ingress) which I did. I keep getting errors though, I pasted below, I tried googling around but I am not familiar enough with kubernetes to navigate the issue.
Please advise :)
cert-manager % kubectl describe clusterissuer,certificate,order,challenge
Name: letsencrypt-prod
Namespace:
Labels: <none>
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"ClusterIssuer","metadata":{"annotations":{},"name":"letsencrypt-prod"},"spec":{"acme":...
API Version: certmanager.k8s.io/v1alpha1
Kind: ClusterIssuer
Metadata:
Creation Timestamp: 2019-11-30T09:27:11Z
Generation: 2
Resource Version: 86328
Self Link: /apis/certmanager.k8s.io/v1alpha1/clusterissuers/letsencrypt-prod
UID: 963baf6b-1353-11ea-94ad-42010a8a0173
Spec:
Acme:
Email: wahyu@incredibly.io
http01:
Private Key Secret Ref:
Key:
Name: letsencrypt-prod
Server: https://acme-v02.api.letsencrypt.org/directory
Status:
Acme:
Uri:
Conditions:
Last Transition Time: 2019-11-30T09:27:11Z
Message: Failed to verify ACME account: acme: urn:ietf:params:acme:error:rateLimited: Your ACME client is too old. Please upgrade to a newer version.
Reason: ErrRegisterACMEAccount
Status: False
Type: Ready
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ErrVerifyACMEAccount 15m (x3 over 15m) cert-manager Failed to verify ACME account: acme: urn:ietf:params:acme:error:rateLimited: Your ACME client is too old. Please upgrade to a newer version.
I was following this tutorial: https://www.youtube.com/watch?v=APnXlMiKBWg&list=WL&index=30&t=0s
everything works until the cert thing, the presenter was mentioning that the order of executing matters (apply the certs first THEN ingress) which I did. I keep getting errors though, I pasted below, I tried googling around but I am not familiar enough with kubernetes to navigate the issue.
Please advise :)