Goal:

As an administrator, I would like to use the installer-provisioned infrastructure deployment method for deploying OpenShift with a custom cluster domain name and API port number.

Problem:

By default the cluster gets set up with the following DNS structure:

```
API DNS: api.<clustername>.<basedomain>
API-INT: api-int.<clustername>.<basedomain>
Wildcard Apps DNS: *.apps.<clustername>.<basedomain>
```

For a number of reasons (including restrictions related to organizational DNS policies), many customers would prefer to create the cluster without having the  <clustername> in the domain or even define a custom domain name for OpenShift to use.

```
API DNS: api.<basedomain>
API-INT: api-int.<basedomain>
Wildcard Apps DNS: *.<basedomain>
```

This would mean the console would be reachable at:

```
https://console-openshift-console.exampledev.com
```
and not

```
https://console-openshift-console.apps.myclustername.exampledev.com
```

However,  <clustername> is not an optional part of the domain name and must be included into the install-config.yaml.

In addition, customers would like the ability to change api-server port from 6443 to any other port, like 443. This was possible on 3.x, but not on 4.x.

Why is this important:

• Many customers have restrictive organizational DNS policies prohibiting access to non-common port numbers or more than 3 levels of subdomains.

 
Lifecycle Information:

• Core

Previous Work:

Dependencies:

• None

Prioritized epics + deliverables (in scope / not in scope):

• Allow customization of the cluster domain name at install
• Allow a custom port number to be used for api/api-int access

Estimate (XS, S, M, L, XL, XXL):

Customers:

Open questions: