-
Notifications
You must be signed in to change notification settings - Fork 45
Administering our production environment
See here
kubectl -n production get pods
or kubectl -n staging get pods
To reboot a server, from the Google Cloud project console, navigate to the pod (not deployment) that is having problems, and delete the pod (not the deployment)
Go to the deployment page on Google Cloud Console and click "container logs"
Or to view at the console, kubectl -n production logs -f [tab-complete]
Environment variables are set per-pod in individual yaml files, e.g. frontend-deployment.yaml
To view current values, you can do kubectl -n production exec -it frontend-deployment-644866b6d4-fcmh7 env
for a particular pod.
Many environment variables are secrets, which can be set through kubectl like this: kubectl edit secret cjw-intercom-secret --namespace production
or through Google Cloud console