The certificates get properly picked up when I restart the origin docker
container, but I observed that this procedure seems to imply a short
downtime (when not running a HA setup).
Is there a way to have the daemon process pick up the new certificates
without a downtime in my scenario?
Clayton Coleman <ccole...@redhat.com> schrieb am Di., 6. März 2018 um
> Even when you restart, you aren’t seeing the new certs loaded?
> On Mar 5, 2018, at 2:58 AM, Alex Stockinger <dajudge...@gmail.com> wrote:
> I am trying to secure my OpenShift installation's Console / API on port
> 8443 with let's encrypt certificates. I got this working nicely using the
> servingInfo/namedCertificates section in the master-config.yaml file.
> However upon certificate renewal the process doesn't seem to pick up the
> new certificates.
> So my question is: is there a (downtime-free) way to trigger a reload of
> the certificates used for port 8443?
> Thanks in advance for your help!
> users mailing list
users mailing list