These will be labelled ‘tl’,’td’ and ‘tp’. These will (potentially) each have different parameters and settings, so the first task is to create a settings file (secrets.js) which will be shared between all apps in this project and which partitions the parameters into local, development and production. I generally have 3 different environments for testing locally, testing in docker and Kubernetes, and a final version. Set up credentials and check cluster looks ok gcloud container clusters get-credentials sensor -zone europe-west4-bĪssign yourself as admin kubectl create clusterrolebinding cluster-admin-binding -clusterrole=cluster-admin Staging, dev, production So first, let’s get a small cluster up and running in your cloud project gcloud beta container -project "yourproject" clusters create "sensor" \ I always find it easier to create Kubernetes stuff through gcloud and kubectl rather than using the UI in the cloud console. The code for this entire project is at Kubernetes clusterįor testing, I’m using a preemptible cluster to keep the costs down.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |