From 04a9b4502372167a9596bf0af2d81a13da94b03b Mon Sep 17 00:00:00 2001
From: YuviPanda <yuvipanda@gmail.com>
Date: Wed, 4 Dec 2024 14:02:31 -0800
Subject: [PATCH] Explicitly document that the default cloud provider is AWS

GKE is a superior experience, but unfortunately Google's
Customer Support leaves a lot to be desired. EKS has mostly
caught up, and EFS is doing much better than GCP Filestore.

This is one (but not the primary outcome) from
https://github.com/2i2c-org/infrastructure/issues/4993
---
 docs/hub-deployment-guide/runbooks/phase1/index.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/hub-deployment-guide/runbooks/phase1/index.md b/docs/hub-deployment-guide/runbooks/phase1/index.md
index 03db688762..218b869d24 100644
--- a/docs/hub-deployment-guide/runbooks/phase1/index.md
+++ b/docs/hub-deployment-guide/runbooks/phase1/index.md
@@ -18,6 +18,11 @@ The following lists the information that needs to be available to the engineer b
 - Community Representatives
 - Technical Contacts added to Airtable?
 
+## Default cloud provider
+
+*If* the community has no particular preference for a cloud
+provider, we will default to using AWS.
+
 ## Outputs
 
 At the end of Phase 1, all engineers should have access to the cloud account where the new cluster and hub will be deployed to.