Page Comparison

...

1. Keep CMPv2 server details in e.g. ESR
2. Support configurable output type to output artifacts in desired format: JKS, P12 or PEM - implemented in Guilin release
   
3. Certificate update implementation on server and client side
   1. Add to CertService new endpoint to call certificate update in CMPv2 server
   2. Adjust CertService's client to work as sidecar, not init container

      1. CerService's client adjusted to run in loop (e.g. keep watermark and read it in every run)

         1. If certificate is not enrolled - request certificate
         2. If certificate is already enrolled - request certificate update
   3. Application adjusted to reload keystore/truststore in the runtime or if such is not possible, adjusted to restart itself or inform K8s via probes mechanism that restart is required
4. Adjust logging to ONAP guidance
5. CMPv2 over HTTPS support