search

nerc-project / operations

Issues related to the operation of the NERC OpenShift environment
2 stars 0 forks source link

Allocate dns records and route53 credentials for hypershift cluster #743

Closed larsks closed 1 month ago

larsks commented 1 month ago

When we first built the hypershift cluster, we were not able to manage DNS records for the nerc.mghpcc.org domain, so it was not possible to use generate wildcard certificates using lets encrypt. The cluster was deployed using the int.massopen.cloud domain. Now that we have route53 set up correctly, I would like to move the cluster to the nerc.mghpcc.org domain:

  1. I would like the subdomain hypershift1.nerc.mghpcc.org for the cluster, and
  2. Appropriate route53 credentials for cert-manager to interact with lets encrypt dns-01 challenges
  3. DNS records for the cluster vips (to be allocated in #742)
    • api.hypershift1.nerc.mghpcc.org
    • *.apps.hypershift1.nerc.mghpcc.org
jtriley commented 1 month ago

@larsks This should be all set. Credentials are in vault: hypershift1/aws-route53-credentials.

$ dig +short test.apps.hypershift1.nerc.mghpcc.org
10.30.8.81

$ dig +short api.hypershift1.nerc.mghpcc.org
10.30.8.80
larsks commented 1 month ago

@jtriley thanks! This will do for now, but the goal is that the dns names ultimately point to public ip addresses (see (3) in the issue description).

joachimweyl commented 1 month ago

@larsks shall we leave this open or close this and open a new issue to deal with pointing to public IP addresses?

jtriley commented 1 month ago

@joachimweyl Let's leave it open until I get public addresses setup. I'll try to get this closed today.

larsks commented 1 month ago

Thanks @jtriley!