From 9413f55f7f7b548b441c2d1bc3aa20be18abdedd Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Thu, 17 Mar 2022 15:52:09 -0700 Subject: [PATCH] Move a few hubs off *.pilot.2i2c.cloud To signal that this is reasonably stable infrastructure, we're removing 'pilot' from a few domain names. I've setup a wildcard domain *.2i2c.cloud to point to the pilot-hubs cluster's nginx-ingress service IP, so merging this would just switch out these 3 hubs to get rid of the .pilot part of their domain. This does mean our 'primary' cluster becomes a bit more important, so we should make it a little more resilient. See https://github.com/2i2c-org/infrastructure/issues/1105 and https://github.com/2i2c-org/infrastructure/issues/1102 Ref https://github.com/2i2c-org/infrastructure/issues/989 --- config/clusters/2i2c/cluster.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/config/clusters/2i2c/cluster.yaml b/config/clusters/2i2c/cluster.yaml index 49f5628752..2ac8cee0ea 100644 --- a/config/clusters/2i2c/cluster.yaml +++ b/config/clusters/2i2c/cluster.yaml @@ -12,7 +12,7 @@ support: hubs: - name: staging display_name: "2i2c staging" - domain: staging.pilot.2i2c.cloud + domain: staging.2i2c.cloud helm_chart: basehub auth0: # connection update? Also ensure the basehub Helm chart is provided a @@ -25,7 +25,7 @@ hubs: - staging.values.yaml - name: dask-staging display_name: "2i2c dask staging" - domain: dask-staging.pilot.2i2c.cloud + domain: dask-staging.2i2c.cloud helm_chart: daskhub auth0: # connection update? Also ensure the basehub Helm chart is provided a @@ -38,7 +38,7 @@ hubs: - dask-staging.values.yaml - name: demo display_name: "2i2c demo" - domain: demo.pilot.2i2c.cloud + domain: demo.2i2c.cloud helm_chart: basehub auth0: # connection update? Also ensure the basehub Helm chart is provided a