search

jmo808 / arm-aro43

9 stars 9 forks source link

Make Custom Domain Optional #4

Open carthikannayan opened 3 years ago

carthikannayan commented 3 years ago

Hi @jmo808 @ehashman: Can you guys able to guide how I could make the custom domain an optional field on this ARM template, please? Any help is much appreciated.

ehashman commented 3 years ago

Hi @carthikannayan, I'm no longer with the ARO team. I suggest you reach out to e.g. @mjudeikis or @jim-minter.

carthikannayan commented 3 years ago

Thanks @ehashman !

mjudeikis commented 3 years ago

@carthikannayan can you be more specific what do you want to achieve?

jmo808 commented 3 years ago

@carthikannayan That domain field is used for either the cluster fqdn prefix or for a full custom domain. I don't think any changes are needed to this template in order to achieve what you are looking for. The az cli generates a random id for that field if none is provided so you can just generate a random id yourself if you are looking for a similar experience to the cli.

carthikannayan commented 3 years ago

@carthikannayan can you be more specific about what do you want to achieve?

Hi @mjudeikis: Apologies for the delayed response, This template won't let me provision the ARO Cluster if I don't supply a domain name. I was asking if the domain name can be made optional, that way I can provision and access the Cluster using the openshift console. Right now, irrespective of public or private cluster deployment, I need to supply a domain name and can't log in to the cluster URL. I might need a bastion host to be able to log in.

Thanks, Carthik

carthikannayan commented 3 years ago

@carthikannayan That domain field is used for either the cluster fqdn prefix or for a full custom domain. I don't think any changes are needed to this template in order to achieve what you are looking for. The az cli generates a random id for that field if none is provided so you can just generate a random id yourself if you are looking for a similar experience to the cli.

@carthikannayan That domain field is used for either the cluster fqdn prefix or for a full custom domain. I don't think any changes are needed to this template in order to achieve what you are looking for. The az cli generates a random id for that field if none is provided so you can just generate a random id yourself if you are looking for a similar experience to the cli.

@jmo808 : If I leave the field blank, then the cluster provisioning fails.