This section documents testing clusters and deployments.

Create a project in the "Engineering Projects" folder

Create a folder with your name here following our naming conventions. If you are an Support Engineer wishing to start your own project, ask for one to be created in the #dev-chat channel on slack. When you are done with the project, let #delivery know in the same thread you started in #cloud-devops so that they know it is safe to take it down.

How to manually start a test cluster in your test project in GCP

• Go to your project
• Click create a cluster.
• Give it a name (a good convention is to prefix with your username).
• Keep the defaults zonal and us-central1.
• Set the default pool to 3 nodes.
• Change machine type to n1-standard-16.
• Click "Create Cluster".
• When cluster is ready, click connect and copy/paste the command and execute it (it looks something like gcloud container clusters get-credentials ....). Now kubectl is acting on this cluster.
• Give yourself admin superpowers by executing:

kubectl create clusterrolebinding cluster-admin-binding --clusterrole cluster-admin --user $(gcloud config get-value account)

• Add a storage class by saving these contents

kind: StorageClassapiVersion: storage.k8s.io/v1metadata:  name: sourcegraph  labels:    deploy: sourcegraph-storageprovisioner: kubernetes.io/gce-pdparameters:  type: pd-ssd # This configures SSDs (recommended).

into a file 'sourcegraph.Storageclass.yaml' and executing

kubectl apply -f sourcegraph.Storageclass.yaml

• cd to your clone of deploy-sourcegraph and follow the remaining steps of the installation.

./kubectl-apply-all.sh