Ugly Command Party - Day 3

On the 3rd of the ugly command party, the command I'll share is:

Ugly Command Name: Find Failed Certificate Requests and Identify Issues?

What does it do?

For users of #certmanager running in #kubernetes, this will fetch all unready certificate requests in a namespace and identify:

• The certificate & certificate request name
• The reasons why they are not ready
• The approval status

When would you use it?

If you’re having troubles determining why your ingress object or application is not receiving a valid SSL certificate, this should quickly help identify where to look next. The message details typically include a helpful pointer to the root cause of the issue.

What is the command?

Please view the GitHub Gist below to find the code snippet. Due to a limitation with LinkedIn, it does not accept some code in the code snippet and breaks the Article feature :-/

What is some sample output?

---
CertificateRequest: failed-crt-ggvqv
Certificate: failed-crt
Issuer: letsencrypt-prds
Ready Status: False
Ready Message: Referenced "Issuer" not found: issuer.cert-manager.io "letsencrypt-prds" not found
Approved Status: True
Approved Message: Certificate request has been approved by cert-manager.io
---
CertificateRequest: failed-crt2-2k6tx
Certificate: failed-crt2
Issuer: letsencrypt-staging
Ready Status: False
Ready Message: Waiting on certificate issuance from order failed/failed-crt2-2k6tx-1415849869: "pending"
Approved Status: True
Approved Message: Certificate request has been approved by cert-manager.io        

What does it need?

• kubectl
• jq

I you want this command tailored for your environment and ready to copy & paste, this command has been added to the open source library of commands available through RunWhen Local. Check it out here: https://docs.runwhen.com/public/runwhen-local/getting-started/running-locally

Find an example of the command here: https://runwhen-local.sandbox.runwhen.com/failed/failed-SSL-Certificate-Health/#find-failed-certificate-requests-and-identify-issues

Have an ugly command to share? Collaborate with us on GitHub with issues or discussions

This is part of a series.?Check out?this article?to see additional ugly commands posted in the series.