The EJBCA Certificate Signing Request Proxy for K8s forwards certificate signing requests generated by Kubernetes to EJBCA for signing by a trusted enterprise certificate authority. The signer operates within the K8s CertificateSigningRequests API and implements a Controller that uses the the V1 CertificateSigningRequests informer to handle associated resources. CSRs are only enrolled if they are approved using an approver.
TODO Requirements is a required section
- Getting Started
- Usage
- Testing
- License
The EJBCA CSR Signer v2.0 has breaking changes from v1.0. To migrate from v1.0 to v2.0, uninstall the v1.0 deployment and install the v2.0 deployment. The v2.0 deployment uses the same configuration as v1.0, but the configuration is now stored in a Kubernetes ConfigMap. See the Getting Started to install the v2.0 deployment.
In the Keyfactor Community, we welcome contributions. Keyfactor Community software is open-source and community-supported, meaning that no SLA is applicable. Keyfactor will address issues as resources become available.
- To report a problem or suggest a new feature, go to Issues.
- If you want to contribute bug fixes or proposed enhancements, see the Contributing Guidelines and create a Pull request.
Commercial support is available for EJBCA Enterprise.
For license information, see LICENSE.
See all Keyfactor EJBCA GitHub projects.