Skip to content

Latest commit

 

History

History
35 lines (29 loc) · 1.41 KB

File metadata and controls

35 lines (29 loc) · 1.41 KB

Adding PTR records for platform=none CI clusters in vSphere

WMCO' CSRs approver requires reverse DNS lookup for each Windows instance that joins the cluster as a Windows worker. For CI clusters with platform-agnostic infrastructure (platform=none) a fixed lease pool is configured to ensure latter requirement is met.

The create-ptr-records.sh script enables the reverse DNS lookup by creating PTR records for each IP address available in the selected subnets.

vSphere CI (vmc-ci.devcluster.openshift.com) uses AWS Route53 for DNS resolution and the following ci-segments are reserved for platform=none clusters

  • ci-segment-56
  • ci-segment-47
  • ci-segment-58
  • ci-segment-59

each segment sits on a /27 subnet (192.168.x.1/27) with DHCP range from 192.168.x.10 to 192.168.x.30, where x accounts for the third octet and matches the number of the ci-segment, from 56 to 59 inclusive. DNS is provided by the VPC with server IP 10.0.0.2.

Before running the create-ptr-records.sh script, ensure AWS CLI is properly configured with AWS credentials and region for openshift-vmware-cloud-ci account, for example:

# configures AWS CLI
export AWS_PROFILE="openshift-vmware-cloud-ci"
export AWS_REGION="us-west-2"

# run script
./create-ptr-records.sh

where openshift-vmware-cloud-ci is the name of profile that contains the credentials, and us-west-2 is the region where the resources were provisioned.