Update DNS Records for old branches to new Netlify

[thesuperzapper]

As part of cleanup work to ensure Google only indexes the latest version of the Kubeflow website, we discovered that some very old “Version SNAPSHOT” subdomains point to the wrong Netlify instance.

This means our updates to the old branches are not reflected.

Important Notes

• As with any DNS changes, there will be some issues during the transition.
• Because we only keep these domains for archival purposes, we are not concerned if they become unavailable for some time. Plus, if something goes horribly wrong, we can use the reference below to revert the changes.
• In this case, the new Netlify will need to provision SSL certificates for these domains (which should happen automatically after some time). This means the old domains will temporarily show SSL errors, this is expected.

DNS Updates

We would like to request the following DNS record updates:

TYPE	NAME	OLD VALUE	NEW VALUE
CNAME	v0-2.kubeflow.org	eager-nobel-1708cf.netlify.com	v0-2--competent-brattain-de2d6d.netlify.app
CNAME	v0-3.kubeflow.org	competent-jones-a15cc2.netlify.com	v0-3--competent-brattain-de2d6d.netlify.app
CNAME	v0-4.kubeflow.org	infallible-hermann-cb44b2.netlify.com	v0-4--competent-brattain-de2d6d.netlify.app
CNAME	v0-5.kubeflow.org	practical-neumann-e70801.netlify.com	v0-5--competent-brattain-de2d6d.netlify.app
CNAME	v0-6.kubeflow.org	v0-6-branch--competent-brattain-de2d6d.netlify.com	v0-6--competent-brattain-de2d6d.netlify.app
CNAME	v0-7.kubeflow.org	v0-7-branch--competent-brattain-de2d6d.netlify.com	v0-7--competent-brattain-de2d6d.netlify.app

[thesuperzapper]

I have made these DNS updates on the GCP account kubeflow-dns, but the site is still not showing the updates.

I have reached out to Netlify support to check if they need to trigger a transfer on their end.

[thesuperzapper]

Ok, so the issue was that Netelify needs the subdomain to be the same as the branch name it CNAME targets, which means we needed to create copies of our v0.2-branch called things like v0.2, and then CNAME to the branch deploy of those branches instead.

[thesuperzapper]

This is resolved.