This guide offers recommended configurations and settings unique to the Openshift Container Platform (OCP). These should be used to augment the generic requirements offered on our primary requirements page.

​
DNS / SSL

OpenShift imposes a unique subdomain structure to the applications that run on its clusters; for example: 
anaconda.apps.openshift.example.com
*.anaconda.apps.openshift.example.com
When creating the SSL certificate, make sure that they are constructed for this multi-level domain name.
Note that even though your OCP cluster may already be configured to serve SSL, Anaconda Enterprise will still require its own SSL certificate due to the usage of wildcards.

​
Helm chart customization

OpenShift uses a different DNS server address than the one assumed by default in the helm chart. To ensure that the application uses the proper address, add the following lines, respecting indentation, to your values.yaml overrides file: 
git:
  default:
    proxy:
      dns-server: dns-default.openshift-dns.svc.cluster.local