search

nerc-project / operations

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

Delegate nerc.mghpcc.org to nerc route53 nameservers #620

Open larsks opened 6 days ago

larsks commented 6 days ago

Delegate the nerc.mghpcc.org domain to route53 domain(s) managed by the NERC so that the nerc-dns repository can populate new records in nerc.mghpcc.org.

jtriley commented 5 days ago

I currently have a ticket submitted to elevate my privileges to manage IAM users in our "prod" AWS account. In the meantime, @culbert is adding the DNS records mentioned here by hand: https://github.com/nerc-project/operations/issues/619 although with the following changes given that having NERC in the name isn't really necessary given the subdomain:

api.ocp-test-2 128.31.20.90
api-int.ocp-test-2 192.168.50.250
*.apps.ocp-test-2 128.31.20.112

He's also getting me the current zone files for the nerc.mghpcc.org subdomains and the policy attached to the route53 user(s) we use to manage letsencrypt. We plan to meet later this week when the ticket I have open gets addressed and set up proper delegation for the nerc.mghpcc.org subdomain.

We will also, at that time, update the {keycloak, regapp, coldfront}.mss.mghpcc.org A records in MGHPCC's route53 instance to be CNAME's to {keycloak, regapp, coldfront}.nerc.mghpcc.org so that those names persist but the addresses live in the delegated zone.

tssala23 commented 5 days ago

Thank you very much @jtriley and @culbert. Will close #619 now