1)  Follow the instructions in the NRO generator to generate the new environment. If all is successfull, you should end up with 2 environments (the dev and staging) . When finished, run a normal k8s production deployment for your site, so that the master site gets created.

2) Switch to the helper scripts directory

To configure the development site

3) Connect your kubernetes to the development

//get connected to google cloud development cluster:
gcloud container clusters get-credentials p4-development --zone us-central1-a --project planet-4-151612

//Start using the development cluster
kubectl config set-context p4-develop --namespace=develop --cluster=gke_planet-4-151612_us-central1-a_p4-development --user=gke_planet-4-151612_us-central1-a_p4-development

//switch to our own context
kubectl config use-context p4-develop


4) List the helm releases:

helm ls

5) Find out the release you just created and copy it (you will need it later)

6) run:


7) You will be asked to create oAuth gcloud ID and Secret. Follow the urls and do them (Check one of the existing ones for the values)

Keep a note of the ID and secret because you are going to need it for the staging and production sites as well

7) Follow all the instructions

8) run:



To configure the staging and production sites:

Switch to the production cluster:

//get connected to the google cloud for the production cluster
gcloud container clusters get-credentials planet4-production --zone us-central1-a --project planet4-production

//or if i wanted a specific site context for the release. (replace the "koyansync" bellow with your site):
kubectl config set-context planet4-koyansync-master --namespace koyansync --cluster gke_planet4-production_us-central1-a_planet4-production --user gke_planet4-production_us-central1-a_planet4-production

//switch to that context (replace the "koyansync" bellow with your site):
kubectl config use-context planet4-koyansync-master

And then repeat steps 4-8 above, once for each of the two releases (“release” and “master”)