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
Currently when using PKI mode the server.ca and ca.crl files must be present at daemon start up.
It is already possible to replace the cluster certificate at runtime via /1.0/cluster/certificate. This writes the cluster certificate to disk and updates the network certificate on the TLS listener (and forwards the request to other cluster members to do the same).
We can improve PKI mode by allowing a similar update of the server.ca and ca.crl files. In particular for the ca.crl, this would allow certificate revocation without restarting LXD.
This can be in the form of a PATCH /1.0/cluster/certificate endpoint which only updates non-empty fields, and includes cluster_key, cluster_cert, cluster_ca, and cluster_crl fields.
The text was updated successfully, but these errors were encountered:
Currently when using PKI mode the
server.ca
andca.crl
files must be present at daemon start up.It is already possible to replace the cluster certificate at runtime via /1.0/cluster/certificate. This writes the cluster certificate to disk and updates the network certificate on the TLS listener (and forwards the request to other cluster members to do the same).
We can improve PKI mode by allowing a similar update of the
server.ca
andca.crl
files. In particular for theca.crl
, this would allow certificate revocation without restarting LXD.This can be in the form of a
PATCH /1.0/cluster/certificate
endpoint which only updates non-empty fields, and includescluster_key
,cluster_cert
,cluster_ca
, andcluster_crl
fields.The text was updated successfully, but these errors were encountered: