hyperledger
fabhttp endpoint will need to restart on certificate renewals
fabhttp server loads static TLS certificates in the server here. This will require restart of the server when the certificates are renewed or replaced.
It will be better if the certificates are loaded dynamically as they are loaded in grpc server here to not require a restart.
But Fabric cannot dynamically update a TLS certificate anyway... there is no API for that.
if fabric is running in kubernetes and the secret containing the certificate is updated, grpcserver can pick up the new certificate without any restarts needed.
if fabric is running outside of kubernetes and the file with the certificate is updated with new certificate, gpcserver can pick up the new certificate without any need of restarting the server.
I'm pretty sure the file is loaded only at startup... and not upon every TLS handshake.