GitLab / Support-resources

This is a demo of what the next iteration of Support-Resources looks like. I'm using the Cloud Sandbox to create a Terraform projects (from predefined templates) that then automatically provisions resources within my personal GCP project.

More info about the Cloud Sandbox: https://about.gitlab.com/handbook/infrastructure-standards/realms/sandbox/

Link to the performed workarounds: https://gitlab.com/gitlab-com/business-technology/engineering/infrastructure/issue-tracker/-/issues/86#note_755209745

TIMESTAMPS

About Sandbox Cloud - 00:00
The Support-Resources-Template initial set-up - 01:28
Applying the 2 Sandbox workarounds - 06:08
The Service Account workaround - 07:29
The DNS subdomain and managed zone workaround - 09:36
Running the Terraform Dry-run stage and starting the Apply - 13:08
Successful completion of Terraform Apply and starting Terraform Destroy - 17:23
Info about the design of the Support Templates in Sandbox Cloud - 18:12

Hi, this is Vlad from Gitlab Support and in this clip Rocky and I create a couple of GKE clusters and and inspect the Gitlab deployment from one of those clusters.

Pre reqs: kubectl, helm, gcloud

Commands used (similar to):

helm upgrade --install gitlab gitlab/gitlab --timeout 600s --set global.hosts.domain=vlad-gke-gitlab62.sr.gitlab.support --set global.hosts.externalIP=34.91.218.78 --set certmanager-issuer.email=vlad@example.com --version 4.11.2

kubectl get secrets sh.helm.release.v1.gitlab.v1 -o jsonpath='{.data.release}' | base64 -D | base64 -D | gzip -d | jq

Here's a clip where Silvester and I do the same thing manually: https://www.youtube.com/watch?v=XcJqIggsJ5E