add infrastructure dir with documentation

processing · Oct 25, 2022 · 3639fb4 · 3639fb4
1 parent 081cffa
commit 3639fb4
Show file tree

Hide file tree

Showing 11 changed files with 30 additions and 0 deletions.
diff --git a/infrastructure/README.md b/infrastructure/README.md
@@ -0,0 +1,30 @@
+## Quickly Rolling Back a Deploy
+
+1. Since the latest tag is being used, we can't simply just repoint the image back to the previous release, but we can instead use Kubernetes' built in rollback feature.
+1. `kubectl rollout undo deployment.apps/web-editor-node -n production`
+
+## Upgrading the GKE Cluster
+
+1. Log into the [Google Cloud Platform console](https://console.cloud.google.com/) and go to the GKE service and click into the p5-gke-cluster.
+1. There are two components of GKE that need to be upgraded, the control plane (or cluster master node), and the cluster nodes themselves (or node pools), in that order.
+
+### Upgrading the GKE control plane
+
+1. Upgrade the GKE control plane first, by following the steps below.
+![GKE control plane upgrade 1](./images/control_plane_upgrade_1.png)
+1. Look up the latest available version in the [Kubernetes release changelog](https://kubernetes.io/releases/) to determine if there are any breaking changes that will require updates to your manifest files. Based on this information, determine the version you want to upgrade the cluster to (ideally the latest supported version) and hit save changes. This should begin the control plane upgrade. Since this is a regional cluster, there should be no downtime during this process however, the API will be unavailable, so do not attempt a deploy during the upgrade.
+![GKE control plane upgrade 2](./images/control_plane_upgrade_2.png)
+
+### Upgrading the GKE node pool
+
+1. Wait until the GKE control plane upgrade is complete and then proceed by upgrading the GKE node pool using the following steps.
+1. Navigate to the workloads page to make sure that you have a few replicas (pods) of each service running in the cluster so that the node draining process doesn't cause downtime.
+1. Navigate back to the main GKE service page where you see the cluster listing and you should see that there is an update available.
+![GKE node pool upgrade 1](./images/node_pool_upgrade_1.png)
+1. Select the version that is the same as the control plane.
+![GKE node pool upgrade 2](./images/node_pool_upgrade_2.png)
+
+### Update the version in the terraform
+
+1. Since we've done the upgrade manually, the terraform file should be updated to reflect the current version in case we need to recreate the cluster from scratch.
+1. Update the default GKE version [here](https://github.com/processing/p5.js-web-editor/blob/develop/terraform/variables.tf#L13).
diff --git a/infrastructure/images/control_plane_upgrade_1.png b/infrastructure/images/control_plane_upgrade_1.png
diff --git a/infrastructure/images/control_plane_upgrade_2.png b/infrastructure/images/control_plane_upgrade_2.png
diff --git a/infrastructure/images/node_pool_upgrade_1.png b/infrastructure/images/node_pool_upgrade_1.png
diff --git a/infrastructure/images/node_pool_upgrade_2.png b/infrastructure/images/node_pool_upgrade_2.png
diff --git a/terraform/.terraform.lock.hcl → infrastructure/terraform/.terraform.lock.hcl b/terraform/.terraform.lock.hcl → infrastructure/terraform/.terraform.lock.hcl
diff --git a/terraform/README.md → infrastructure/terraform/README.md b/terraform/README.md → infrastructure/terraform/README.md
diff --git a/terraform/backend.tf → infrastructure/terraform/backend.tf b/terraform/backend.tf → infrastructure/terraform/backend.tf
diff --git a/terraform/main.tf → infrastructure/terraform/main.tf b/terraform/main.tf → infrastructure/terraform/main.tf
diff --git a/terraform/variables.tf → infrastructure/terraform/variables.tf b/terraform/variables.tf → infrastructure/terraform/variables.tf
diff --git a/terraform/vpc.tf → infrastructure/terraform/vpc.tf b/terraform/vpc.tf → infrastructure/terraform/vpc.tf