Move nasa-veda hub URL

[yuvipanda]

We keep redirects in place from the old URL, in case there are external links already present.

The OAuth callback URL needs to be changed at
https://github.com/organizations/2i2c-org/settings/applications/2096065 just before merging.

Ref #3029

[github-actions]

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider	Cluster Name	Upgrade Support?	Reason for Support Redeploy	Upgrade Staging?	Reason for Staging Redeploy
aws	nasa-veda	Yes	Following helm chart values files were modified: support.values.yaml	Yes	Following helm chart values files were modified: staging.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	nasa-veda	prod	Following helm chart values files were modified: prod.values.yaml

[yuvipanda]

Let's wait for explicit approval in #3029 (comment) before going through with this.

[yuvipanda]

@freitagb is going to use this as an opportunity to use a brand new domain. So let's hold off for a bit more.

[consideRatio]

Suggested change

	to: staging.veda.2i2c.cloud
	to: staging.veda.2i2c.cloud
	- from: grafana.nasa-veda.2i2c.cloud
	to: grafana.veda.2i2c.cloud

Let's get grafana updated as well (and the associated callback URL for the oauth2 application)

[consideRatio]

I think there could be merge conflicts or config-conflicts caused by #3075, where I added a redirect from staging.nasa-veda.2i2c.cloud to staging.veda.2i2c.cloud. The reason I did that was because the hub was currently running at staging.veda.2i2c.cloud and it seemed like the most non-breaking change for now, prompted by having support request saying staging.nasa-veda.2i2c.cloud had issues (because it had moved).

[yuvipanda]

Ping @freitagb - what do we do with this one?

[consideRatio]

Ping @freitagb - should we move forward on this?

[yuvipanda]

I've re-pinged @freitagb on slack now.

[freitagb]

yes, can we move forward with migrating to openveda.cloud?

[freitagb]

@yuvipanda can we use hub.openveda.cloud

[yuvipanda]

Can you put the following CNAMEs in place?

hub.openveda.cloud -> nasa-veda.2i2c.cloud
staging.hub.openveda.cloud -> staging.nasa-veda.2i2c.cloud

Let me know once done, I'll update the PR.

[slesaad]

@yuvipanda done!

[yuvipanda]

@slesaad great, I've updated the PR. Am waiting for the DNS change to propagate (dig doesn't see it yet), will deploy and merge after.

Thank you for the quick response.

[yuvipanda]

@slesaad do you know what the TTLs on those CNAME entries are? I still can't see them, even if I force dig to look at the authoritative nameserver

[slesaad]

@yuvipanda hmm.. 🤔

the ttl is 300 seconds.
anything else that i needed to do on my side?

[yuvipanda]

@slesaad hmm, I'm not sure. I guess I'll just wait a little more and see?

[yuvipanda]

@slesaad they still don't resolve for me - are they resolving for you?

[slesaad]

@yuvipanda they are not 🤔 i wonder why. let me delete and recreate them and see if that helps. I don't know what else to try 😅

[yuvipanda]

@slesaad yeah i don't see it still. I'm not sure what the problem is. I still see it return an NXDOMAIN, which means the authoritative DNS server doesn't think it exists still. Maybe there's an extra 'rollout' step or something? I'm not sure.

I also see that openveda.cloud itself doesn't really resolve to anything, so maybe that's also part of the issue? Whoever is managing that entire domain may be able to help.

[slesaad]

@yuvipanda we're putting in a ticket with AWS to see what's up, I'll let you know when we have more info

[slesaad]

should be working now @yuvipanda !

[github-actions]

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7229399532

[yuvipanda]

Thanks @slesaad!