Copied from #7991:

If you look at https://certbot.eff.org/docs/api/certbot.compat.filesystem.html, you'll notice many formatting errors which should be fixed.

That's the bare minimum which I think should be done, but I think we should also see what we can do to avoid these problems from happening in the future. Is there a way we could build the docs in CI and check for these problems?

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
After Creating a Certificate with a wrong CommonName / DnsName (e.g. hello.k8) an Order is

Beyonce said it best. If you like it then you shoulda put a test on it. Scenarios I like:

• Cert is created with right DN
• Cert is stored to X509Store after creation
• Cert request is not resubmitted
• Handles failures gracefully
• HTTP challenge/response works as expected
• Certificate renewal when cert is about to expiration

Simple read function for pkcs8 files - I've built something for this (in the process of.. simple as), will push for review if successful. Additional function in pem.js

Use case:
Verify/Read any pkcs8 file

Openssl steps

1.) Create a private key pair
openssl req -x509 -newkey rsa:4096 -keyout test.pem -out test.crt -days 365 -subj "/C=Test/ST=Test/L=London/O=Pemjs/OU=Pemjs/CN=Pemjs.com" -