I generated a private key and and a new certificate from SSL.com and now I want to use these to sign the certificates in my Kubernetes cluster. I followed the below method to create the new issuer.
https://cert-manager.io/docs/configuration/ca/
Once I create the new issuer, it gives an error. Any help would be appreciated. Below is the error message.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning ErrInvalidKeyPair 17m (x2 over 17m) cert-manager Error getting keypair for CA issuer: certificate is not a CA
CA certificates have a basicConstraint extension which is set to CA:True. Your normal, run of the mill, end-entity certificate does not have this extension set as above, which is why you are seeing this error. That is, you cannot sign other certificates with an end-entity certificate's private key.
This is by design. A CA is required to certify that the holder of the certificate is who/what they are. They cannot delegate that responsibility to a user who's carried out minimal authentication and simply paid a few dollars/euros/rubles for a certificate. If they permitted this and issued CA certificates to every subscriber, then anyone and everyone could issue themselves certificates that claimed to be from your bank, or from Google etc. - the security of the Internet would soon fail.
Your options are limited: