Re: Custom certificate and the host associated with masterPublicURL

Okay Michael, i understand, thank you for feedback. In this case i think will be reasonable to have a sanity check to fail in case the values are the same - ie enforce it in the code. On Thu, Aug 30, 2018 at 3:40 PM Michael Gugino wrote: > OpenShift components themselves call the masterURL. W

Re: Custom certificate and the host associated with masterPublicURL

I had many issues doing what you suggest, at the beginning I couldn't start the nodes because of the following error : *cannot fetch "default" cluster network: Get https://console:8443/oapi/v1/clusternetworks/default : x509: certificate signed

Re: Custom certificate and the host associated with masterPublicURL

OpenShift components themselves call the masterURL. We ensure that the internal API endpoint is trusted by all OpenShift components. I strongly suggest following the documentation even if it appears to work otherwise, changing this behavior might result in breaking during an upgrade or other scen

Custom certificate and the host associated with masterPublicURL

Hi, I'm trying to understand from a technical point of view the hard requirement around namedCertificates and the hostname associated with the masterPublicURL vs masterURL. According to the docs [1] it says " The namedCertificates section should be configured only for the host name associated wi