Configuring access for Kubectl to private GKE cluster
A guide to how to configure access for Kubectl to private Google Kubernetes Engine cluster with different level of restricted access
This is a quick 1-minute GIF showing a simplified version of the pipeline execution on display at the Armory booth at Kubecon.
You can find a narrated version of this youtube link
In it, we see the components of the pipeline definition:
We also trigger the pipeline, and watch as the dev environment gets updated from the old configuration (
dev: Hello Kubecon!) to a new configuration (
dev: Hello Seattle!). Once an operator has validated that the dev environment is operating as expected, they can go in and approve the manual judgment stage, which starts the promotion to production.
If you’d like to learn more about Spinnaker, or how Armory can help you run Spinnaker at Enterprise Scale, reach out to us at firstname.lastname@example.org!