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.
To get started with the EJBCA Certificate Signing Request (CSR) Proxy for K8s, see Getting started.
For more information on usage, configuration, and integration, see the following links:
To run the EJBCA K8s CSR Signer container a system should fulfill these minimum requirements:
- CPU: 100m
- RAM: 128MB
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.
The Community software is open-source and community-supported, meaning that no SLA is applicable.
- To report a problem or suggest a new feature, go to Issues.
- If you want to contribute actual bug fixes or proposed enhancements, see the Contributing Guidelines and go to Pull requests.
Commercial support is available for EJBCA Enterprise.
For license information, see LICENSE.
See all Keyfactor EJBCA GitHub projects.