Tidy up Pangeo's Namecheap entry and URLs, especially for grafana

[sgibson91]

Summary

There's a bit of a name-clash for the grafana deployment on pangeo-hubs at the moment since I wasn't very clever when setting up the COESSING hub.

infrastructure/config/hubs/pangeo-hubs.cluster.yaml

Lines 13 to 16 in 6cf0a3f

	# This domain should be updated to just grafana.pangeo.2i2c.cloud
	# after the COESSING hub has been brought down and no longer requires
	# grafana.pangeo.2i2c.cloud
	- pangeo-grafana.pangeo.2i2c.cloud

This is the plan for the URLs/Namecheap entry moving forward:

• Migrate and Decommission the COESSING hub #679
• Move pangeo-grafana.pangeo.2i2c.cloud to grafana.gcp.pangeo.2i2c.cloud: Tidy up the Pangeo URLs #847
• Update our A record in Namecheap to be a wildcard record (*.gcp.pangeo) since pangeo-grafana.pangeo.2i2c.cloud, staging.pangeo.2i2c.cloud and pangeo.2i2c.cloud all point to the same IP address. This will be simpler to maintain.
• Update the pangeo.io DNS zone accordingly

If we move forward with #427 at some point, I will make these URLs *.gcp.pangeo so we can have *.aws.pangeo in the future.

[damianavila]

@sgibson91 is there any place in the docs (or maybe is some specific issue) where all the URLs and DNS providers playing together on the pangeo deployment is described. I think I got most of it from reading several related issues but I do not remember one with a short summary (and consolidated information) for the next reader 😉 .

[sgibson91]

No, but in short it is *us-central1-b.gcp.pangeo.io are CNAMES for *gcp.pangeo.2i2c.cloud. Nothing else is going on.

[damianavila]

Great, that was the "missing" implicit (now explicit) thing, I think 😉 .