1. Proposed title of this feature request

Support customizing wildcard certificate in Microshift

2. What is the nature and description of the request?

Microshift includes a basic router deployment with a default wildcard certificate. If a user tries to deploy an alternative certificate by adding a new certificate secret and then updating the router-default to use their secret this change is reverted by Microshift when it is restarted.  

I believe the same will happen if one attempts to replace the default secret but haven't tested it. In general users should be able to provision their own certificates and the default certificate secret should remain the domain of Microshift to manage.

3. Why does the customer need this? (List the business requirements here)

Customers commonly want to use their own CAs and certificates for the wildcard and not rely on a generated self-signed certificate generated by Microshift. As a workaround users could create their own Routes/Ingress with individuall secrets but this entails more effort and management. 

4. List any affected packages or components.

Microshift

OpenShift Ingress