Setup NASA ESDIS cluster and hub

[sgibson91]

ref: #3068

[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-esdis	Yes	Following helm chart values files were modified: enc-support.secret.values.yaml, support.values.yaml	Yes	Following helm chart values files were modified: common.values.yaml, staging.values.yaml, enc-staging.secret.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	nasa-esdis	prod	Following helm chart values files were modified: common.values.yaml, enc-prod.secret.values.yaml, prod.values.yaml

[yuvipanda]

This looks good to me. Thanks for working this through, @sgibson91.

I appreciate that the domain is not called nasa-esdis but just esdis - yay (#3029). I think in the future, we should also not use the word 'nasa' in the name of the cluster itself, so the name matches the domain. But I think it's probably too much hassle to rename and redeploy this one, so I think it's fine to leave this as is. But I'd love for us to put this someplace as a policy so we don't use the 'nasa' prefix next time. Do you think you can help with that as a followup, @sgibson91?

[sgibson91]

@yuvipanda I wrote up #3500 so @damianavila can track it, but I don't think I'll be committing to picking up extra ad hoc work this close to the end of year break, instead focussing on wrapping up what's already on my plate

[github-actions]

🎉🎉🎉🎉

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