Setup development environment
Make sure that your AD user is in the G_GSUITE_YouTeamName AD group. Ask your Team Lead if it was taken care of or open an OfficeIT ticket about it see.
- install/update the gcloud cli
- on MacOS the easiest way to use brew
- run
gcloud init, see Init section in the same guide - run
gcloud auth configure-docker
You will need the gke-gcloud-auth-plugin to authenticate against the clusters. You can find more info about the plugin here
Use the following command to install the plugin:
gcloud components update
gcloud components install gke-gcloud-auth-plugin
If you have access to the clusters (if not, see how to set up a new team) you can connect with the following commands
# connect to the EU West3 production cluster
gcloud container clusters get-credentials gap-production --region europe-west3 --project ems-gap-production --dns-endpoint
# connect to the EU West3 staging cluster
gcloud container clusters get-credentials gap-staging --region europe-west3 --project ems-gap-stage --dns-endpoint
# connect to the US East4 staging clusters primary region
gcloud container clusters get-credentials s-us1-01-gap-primary --region us-east4 --project ems-gap-s-us1-01 --dns-endpoint
# connect to the US East4 production clusters primary region
gcloud container clusters get-credentials p-us1-01-gap-primary --region us-east4 --project ems-gap-p-us1-01 --dns-endpoint
If you have troubles accessing the clusters and know that you should have access, please refer to these tips.
gap-cli installation is explained here
Note1: You need access to the emartech organization on GitHub
Note2: The gap-cli config:edit will open an editor. The opened editor is based on the EDITOR environement variable. If you set EDITOR=vim, the config:edit command will open a vim editor.
k9s installation details can be found here
Our internal guide on how to use k9s can be followed here