Joining as a teammate¶
Once a cluster owner has done the Getting started setup, other teammates can come in with a much shorter onboarding.
What you need from the cluster owner¶
- The R2 access key + secret.
- The name of the AWS profile they used (tip: it's the
r2_aws_profile_defaultvalue ininfra/root.hcl).
That's it. Everything else (Hetzner token, Cloudflare token, cluster SSH key, kubeconfig) lives in R2 and is fetched on demand.
Steps¶
-
Install tools.
See the install links in Getting started. Teammates need the same toolchain as the cluster owner.
-
Add the R2 keys to
~/.aws/credentialsunder the profile name frominfra/root.hcl(r2_aws_profile_default). -
(Optional) Restore the cluster SSH key locally if you need
ssh/scpto nodes. -
(Optional) Fetch the kubeconfig from R2.
The script asks whether to merge the new context into
~/.kube/config. Decline and it writesinfra/dev/.kube/config(mode 600) —export KUBECONFIG=...to use it. SetAUTO_MERGE=1(or0) to skip the prompt. -
You're done. Run Terragrunt as needed.
Multiple environments
Every fetch script takes ENV_DIR=infra/<env>. Swap dev for whichever environment the owner has bootstrapped.
Next steps¶
- Read How it fits together for the Terragrunt graph and module wiring.