While the cluster can operate in a disconnected state, much of the functionality is provided by the connection to GCP. Things like UI integration, policy syncing, Stackdriver, etc. Our early focus is on datacenters that have a connection to the internet. However, we're starting to look a lot more are airgapped environments.
We're going to give a breakout session that goes into more depth on Wednesday @ 4:35pm. IO244.
Some quick details: It's a bit of a split between what GKE runs and what the customer runs. Alpha runs on vSphere 6.5 and we're packing up a Google-hardened OS in much the same way we package GKE for GCP. A lot of the integrations for things like networking and storage will be coming from partners. We'll also have remote mgmt capabilities so we can manage the cluster's control plane in much the same way our SREs do for GKE.
Exactly. This is really the beginning of multi-cluster scenarios that work well across different environments. Failover from on-prem -> GKE is something we're working on.
Masters will run on-prem. We have connection agent that let's us securely talk to the Kube API Server from GCP. We wanted to ensure that the cluster is fully functional even if the connection goes down.
How is Taplytics different than, say, Leanplum. I've seen so many new A/B testing products in the last few months it's hard to keep track of the differentiating features.
I love bourbon and scotch as much as any self-respecting man, but the sheer variety of beer is what makes it my go-to option. There are few things more satisfying than a nice, cold craft beer, even more so when drinking with others as you can take a taste from everyone's glass.