Move from PKCS#1 to PKCS#8 private keys
Closed this issue · 5 comments
Setting the service.beta.openshift.io/serving-cert-secret-name annotation results in a PKCS#1 private key being generated in the secret. PKCS#1 only supports RSA private keys and is no longer supported by some applications (eg. logstash) which now expect the more modern PKCS#8 format for private keys.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
/close
@s-urbaniak: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@jackevans43 please open a bugzilla or a support case. Thank you!