It’s no secret we are Kubernetes and GCloud fans at Cloud 66. We use Kubernetes for our own production environment and GCloud / GKE, Google Cloud’s Kubernetes as a Service for many uses, including as a “playground” cluster for our developers and CI/CD destination for Cloud 66 Skycap.
While both Kubernetes and GCloud provide fine grained access control rights based on roles or G Suite groups, it is possible for an Ops person to have access to the production Kubernetes cluster as well as a non-production cluster. This, combined with the power of Kubernetes configuration files means they might just apply a configuration file to the wrong environment.
While this is no failsafe method for protecting your production environment against human errors, knowing which GCloud and/or Kubernetes context you are on in your bash prompt can only be helpful. I strongly suggest using other methods to protect against mistakenly working against a sensitive cluster / GCloud account as well. Just a disclaimer! (Obviously you can use Cloud 66 Skycap and Cloud 66 Maestro with full ACL and great UI if you wish!).
Now, on to the scripts. Here is how your bash prompt will look if you use the scripts:
And here is how you can do it:
Create file called ~/.kube-prompt.sh with this content and update your .profile as well to update the prompt.
Use Kubernetes and GCloud responsibly!
Originally published at blog.cloud66.com on October 18, 2017.
