Remove pangeo-hubs config files and references

.github/workflows/deploy-hubs.yaml

@@ -227,7 +227,6 @@ jobs:
       failure_nmfs-openscapes: ${{ steps.declare-failure.outputs.failure_nmfs-openscapes }}
       failure_openscapes: ${{ steps.declare-failure.outputs.failure_openscapes }}
       failure_opensci: ${{ steps.declare-failure.outputs.failure_opensci }}
-      failure_pangeo-hubs: ${{ steps.declare-failure.outputs.failure_pangeo-hubs }}
       failure_projectpythia: ${{ steps.declare-failure.outputs.failure_projectpythia }}
       failure_queensu: ${{ steps.declare-failure.outputs.failure_queensu }}
       failure_smithsonian: ${{ steps.declare-failure.outputs.failure_smithsonian }}
@@ -465,7 +464,6 @@ jobs:
       failure_nmfs-openscapes_staging: ${{ steps.declare-failure.outputs.failure_nmfs-openscapes_staging }}
       failure_openscapes_staging: ${{ steps.declare-failure.outputs.failure_openscapes_staging }}
       failure_opensci_staging: ${{ steps.declare-failure.outputs.failure_opensci_staging }}
-      failure_pangeo-hubs_staging: ${{ steps.declare-failure.outputs.failure_pangeo-hubs_staging }}
       failure_projectpythia_staging: ${{ steps.declare-failure.outputs.failure_projectpythia_staging }}
       failure_queensu_staging: ${{ steps.declare-failure.outputs.failure_queensu_staging }}
       failure_smithsonian_staging: ${{ steps.declare-failure.outputs.failure_smithsonian_staging }}

deployer/commands/generate/resource_allocation/daemonset_requests.yaml

@@ -82,12 +82,6 @@ gke:
     cpu_requests: 354m
     memory_requests: 656Mi
     k8s_version: v1.29.1-gke.1589020
-  pangeo-hubs:
-    requesting_daemon_sets: calico-node,fluentbit-gke,gke-metadata-server,gke-metrics-agent,ip-masq-agent,netd,pdcsi-node,support-cryptnono,support-prometheus-node-exporter
-    other_daemon_sets: ""
-    cpu_requests: 354m
-    memory_requests: 656Mi
-    k8s_version: v1.29.1-gke.1589020
 eks:
   # Current overhead is 195m and 250Mi (May 15 2024 with EKS 1.29.4).
   #

docs/topic/infrastructure/config.md

@@ -68,7 +68,7 @@ A hub's helm chart values file can be encrypted as well, following the naming co
 ```
 
 Where we run dedicated clusters that only host a `staging` and `prod` hub, we aggregate all helm chart values shared by each hub into a `common.values.yaml` file, and then describe the helm chart values specific to either `staging` or `prod` with a `staging.values.yaml` or `prod.values.yaml` file respectively.
-See the [Pangeo config](https://github.com/2i2c-org/infrastructure/blob/HEAD/config/clusters/pangeo-hubs/cluster.yaml) for an example.
+See the [Pangeo config](https://github.com/2i2c-org/infrastructure/blob/HEAD/config/clusters/kitware/cluster.yaml) for an example.
 
 ### Conventions for our configuration structure
 

terraform/gcp/cluster.tf

@@ -54,21 +54,22 @@ resource "google_container_cluster" "cluster" {
 
   initial_node_count       = 1
   remove_default_node_pool = true
-  lifecycle {
-    # Any change to the default node_config forces cluster recreation,
-    # and sometimes terraform seems to mess up and think we have changed
-    # something here when we have not. So we explicitly ignore all changes
-    # to node_config - we remove any nodepool it might create with
-    # remove_default_node_pool = true.
-    ignore_changes = [
-      node_config
-    ]
-
-    # An additional safeguard against accidentally deleting the cluster.
-    # The databases for the hubs are held in PVCs managed by the cluster,
-    # so cluster deletion will cause data loss!
-    prevent_destroy = true
-  }
+  deletion_protection = false
+  # lifecycle {
+  #   # Any change to the default node_config forces cluster recreation,
+  #   # and sometimes terraform seems to mess up and think we have changed
+  #   # something here when we have not. So we explicitly ignore all changes
+  #   # to node_config - we remove any nodepool it might create with
+  #   # remove_default_node_pool = true.
+  #   ignore_changes = [
+  #     node_config
+  #   ]
+
+  #   # An additional safeguard against accidentally deleting the cluster.
+  #   # The databases for the hubs are held in PVCs managed by the cluster,
+  #   # so cluster deletion will cause data loss!
+  #   prevent_destroy = true
+  # }
 
   // For private clusters, pass the name of the network and subnetwork created
   // by the VPC