You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, currently step-issuer controller stores each issuer certificate in memory, which causes new certificates to get generated each time the controller is restarted.
This can cause excessive endpoint/certificate charges when using the Smallstep cloud platform
Can we cache the provisioner's certificate as a K8s secret or to an attached PVC?
I linked bellow the location in code where provisioner certificate get generated
This commit removes the requirement of having an identity certificate
per issuer. This certificate was used to make the request "GET /roots"
that might require an mTLS certificate in some deployments. The change
removes these requests and uses the defined bundle in the issuer instead.
Fixes#111
Hi @vanhtuan0409, I've released a new version of step-issuer, v0.8.0, that removes the identity certificate requirement. It also includes a new version of the CRDs. The easiest way to install it is using the helm charts.
Hi, currently step-issuer controller stores each issuer certificate in memory, which causes new certificates to get generated each time the controller is restarted.
This can cause excessive endpoint/certificate charges when using the Smallstep cloud platform
Can we cache the provisioner's certificate as a K8s secret or to an attached PVC?
I linked bellow the location in code where provisioner certificate get generated
https://github.com/smallstep/step-issuer/blob/master/provisioners/step.go#L18
https://github.com/smallstep/step-issuer/blob/master/provisioners/step.go#L74
The text was updated successfully, but these errors were encountered: