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
Which one is the best for me: Helm or Spinnaker?
Both. One complements the other.
Helm strength lies in making manifest bundles (Charts) for multi-environment deployments stress free, componentized, and easily reusable. Helm does this by allowing easy templating of Kubernetes resources. Spinnaker does this also, but at the time of writing this Spinnaker doesn’t provide the ability to template your resources. Helm also gives you the ability to roll out and deploy your applications, but here is where the differeicators start. Scripting your deployment with Helm is very similar to scripting your deployments with Kubernetes manifests. What this means is none of the advanced, zero code, functionality that Spinnaker provides is available. Such as blue/green deployments and automated canary testing.
Spinnaker is a multi-cloud, Kubernetes loving, application delivery powerhouse. It lets Netflix deploy applications 4000 times a day, that is 2.5 deployments a minute, one deployment nearly every 25 seconds. Spinnaker is best in class in deployments and all the functionality it wraps around it. OSS Spinnaker is also great at understanding what other tools do better and incorporating that functionality into its platform. In this case it’s Helm Charts. Isn’t OSS great‽
Check out our blog post on it here:
Base Level of Understanding: This post builds off an understanding of general concepts in Helm Charts, and Spinnaker. If you would like to brush up on these, check out the below links.