Open Edition

I followed the directions to install the Extended Services, Git CORS Proxy, and Canvas on an OpenShift cluster running in VMware. 

When I attempt to add an account to connect to OpenShift, I receive the following error

Replacing the certificate generated by the ingress controller during the OCP setup is not an option.

Is this a known limitation of the Extended Services, or is there a configuration that can skip the certificate validation?

This is a limitation of BAMOE 9.0. On BAMOE 9.1 will have an option to disable TLS certificate validation. I must note, however, that using an invalid certificate is a security concern and should not be done in production or public-facing environments. Here's how the "Connect to OpenShift" modal will look like on BAMOE 9.1.

I followed the directions to install the Extended Services, Git CORS Proxy, and Canvas on an OpenShift cluster running in VMware. 

When I attempt to add an account to connect to OpenShift, I receive the following error

Replacing the certificate generated by the ingress controller during the OCP setup is not an option.

Is this a known limitation of the Extended Services, or is there a configuration that can skip the certificate validation?