Install with Private ClusterType assigns Public IP to bastion node

[smohandass]

Describe the bug
I followed the template and created a openshift environment using clusterType Private. However in the resulting environment, i see the Bastion node is assigned a public Ip by default. When using this template to create an openshift environment on customers system this will be an issue, as they do not want Public IP (internet inbound) access to the cluster. They need the VM's to be accessible only within Customer's network.

To Reproduce
Steps to reproduce the behavior:

1. Created all the pre-requisites for Private ClusterType install such as DNS, vnet, subnect etc..
2. Run the az deployment command

Expected behavior
I expected that the bastion node will not have a public IP assigned. Bastion node is created by the deployment and we have no control.

Screenshots
If applicable, add screenshots to help explain your problem.

stdout
Include the last 100 lines of stdout from Bastion host - see troubleshooting https://docs.microsoft.com/en-us/azure/virtual-machines/linux/openshift-troubleshooting

Template Information (please complete the following information):

• OS: [e.g. iOS]
• Branch: [e.g. master]

Additional context
Add any other context about the problem here.

[haroldwongms]

The OpenShift cluster itself does not have any public IPs. The bastion host is setup with a public IP by default, but you can easily remove the public IP.

[smohandass]

Certain customers have policy restrictions on their azure account which does not let them create public IP's so this template is failing for those scenarios. any workarounds?