AWS binder failing to launch sessions due to SSL certificate problem about pangeo-binder HOT 3 CLOSED

initial cert-manager setup documented here https://github.com/pangeo-data/pangeo-binder/tree/staging/k8s-aws#set-up-https-httpsbinderhubreadthedocsioenlatesthttpshtml

from pangeo-binder.

well, i don't know why these things disappeared but kubectl get crds did not show anything certmanager related.

So I simply re-ran kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v0.11.0/cert-manager.yaml --validate=false followed by kubectl apply -f k8s-aws/binderhub-issuer-prod.yaml and things seem to be working again.

and kubectl get crds shows:

NAME                                   CREATED AT
certificaterequests.cert-manager.io    2020-11-13T22:41:52Z
certificates.cert-manager.io           2020-11-13T22:41:52Z
challenges.acme.cert-manager.io        2020-11-13T22:41:52Z
clusterissuers.cert-manager.io         2020-11-13T22:41:53Z

from pangeo-binder.

@scottyhq nice work getting it functioning. Seems like a bug in cert-manager since it was able to realize you want a cert with the given configuration, but failed to renew it. Perhaps an upgrade to a new version of cert manager is needed - warning: upgrades of cert-manager has been a bit painful in the past due to changes in CRDs etc requiring manual deletion/creation of them etc

from pangeo-binder.