"crit certs renew" fails with default certificate directory structure

[seaunderwater]

Given the following directory structure (default behavior of crit up), the crit certs renew command fails:

/etc/kubernetes/
├── admin.conf
├── controller-manager.conf
├── kubelet.conf
├── scheduler.conf
├── pki
│   ├── apiserver-healthcheck-client.crt
│   ├── apiserver-healthcheck-client.key
│   ├── apiserver-kubelet-client.crt
│   ├── apiserver-kubelet-client.key
│   ├── apiserver.crt
│   ├── apiserver.key
│   ├── auth-proxy-ca.crt
│   ├── auth-proxy-ca.key
│   ├── ca.crt
│   ├── ca.key
│   ├── front-proxy-ca.crt
│   ├── front-proxy-ca.key
│   ├── front-proxy-client.crt
│   ├── front-proxy-client.key

$ crit certs renew
2020-10-07 17:58:33.228354 I | open /etc/kubernetes/pki/admin.conf: no such file or directory

$ crit certs renew  --cert-dir /etc/kubernetes
2020-10-07 18:17:48.063614 I | open /etc/kubernetes/ca.crt: no such file or directory