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
“Can you share with me what you’ve seen as for actual multi-cloud usage from Armory customers?
I know it’s gaining popularity as a criteria, however I’m curious how many companies have actually landed with production workloads running across multiple public clouds. Also, is this typically closer to unrelated departments in organizations running on different clouds, or one team actually deploying to multiple clouds (e.g. one app running simultaneously on GCP/AWS)?”
Yes, we’ve found that almost all large customers (Global 2,000 & up) want to have a single pane of glass (like Armory Spinnaker) across the entire org for deploying workloads to multiple targets & clouds (not just in different parts of the business).
Here’s a sampling of deployment targets across several current Armory customers using our Enterprise Spinnaker platform: