- The argo app is defined at dogfood/kubernetes/argocd and
- The state of the GitLab deployment is configured at dogfood/kubernetes/tooling/gitlab
The confiugration changes to dogfood/kubernetes/tooling/gitlab will be picked up by ArgoCD once it’s landed on the
The admin credential can be found in 1password. If the credential doesn’t work, you may follow https://docs.gitlab.com/charts/quickstart/#sign-in-to-gitlab to recover admin access.
Google OAuth has been configured and you will be able to use your GSuite account to login.
This is only needed for initial deployment
cd into dogfood/kubernetes/argocd and run
kubectl apply -f ./tooling-gitlab.Application.yaml
Automated upgrade is configured for regular version upgrade using
Create a Pull Request to make neccessary changes and ask for review. Once the PR is merged, argocd will sync the new changes to the cluster.
Only use this approach when ArgoCD is down
Switch context to
kubectx gke_sourcegraph-dogfood_us-central1-f_dogfood # or if you don't have kubectx installed # also, you should check it out https://github.com/ahmetb/kubectx kubectl config set current-context gke_sourcegraph-dogfood_us-central1-f_dogfood
Clean up cached
charts directory to avoid stale content
rm -rf charts/
kustomize build --enable-helm ./ | kubectl diff -f -
kustomize build --enable-helm ./ | kubectl apply -f -