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.
Will this be something like COS or even CoreOS? Also, I'm curious to hear more about this part:
> GKE On-Prem has a fully integrated stack of hardened components, including OS, container runtime, Kubernetes, and the cloud to which it connects.
Which runtime are you shipping? CRI-O? What type of outgoing cloud connection is that? I have so many questions. I'm actually at the conference this week if you're willing to grab coffee.
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.
We have an in-house cloud running Kubernetes and we also use Google Cloud with Kubernetes. It is scary to move to GKE in-prem if we do not know pricing.
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.
Will Container-Optimized OS be used as the operating system for on-prem? If so, any plans to spin this off as a more general purpose OS now that it needs to support on-prem use cases?
Hi Weston, I'm exploring and using Istio in the recent months, so what is the advantage of the "Managed Istio(with commercial level support)" over the community version? As I know the community is still actively optimizing the performance, will the Managed Istio have a better performance?
That's not quite a fair comparison. The $35.38 Google price takes advantage of their sustained usage discount, if the instance is running the entire month.
The EC2 price is the full rack rate. You can do better with a spot instance, or by paying up front for a 1-year or 3-year reserved instance.
It's still a stunning price drop from Google. And from my tests, the Google instances give a lot more performance than the supposedly equivalent EC2 instances.
For my projects, Google instances boot faster, have lower network latency, higher network throughput to storage, and more IOPS than EC2 "provisioned IOPS" volumes.
It's really amazing. I can snapshot a 1 TB volume in the US and start a new instance with it in Europe in less than 10 minutes.
There are quite a few cases where you can't or don't want to deal with your instance disappearing at any moment by design (spot) nor with an annual subscription though
I don't like having to commit to an entire year, but reserving that m3.medium brings the price down considerably.
Hopefully AWS will take a look at Google's automatic cuts and think long and hard about it. We're using AWS, but reservations are a constant point of friction for us.
DO is a completely different service. It's Apples to Oranges. You don't go with GC or AWS just for a bare-bones VM, you use them if you already use (or want to use) their greater portfolio of services.
If you are just using EC2 or GC for VM hosting, you are doing it wrong and are throwing away a lot of money.
Sure it's cheaper, but DO doesn't provide consistent performance or security. Look at their past security problems with users able to read others disks or performance benchmarks for proof.
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.
There are a lot of different “flavors” of A/B testing software. We are focused on simple and easy optimization of your mobile apps that can be done by anyone in your organization. The big differentiator for Taplytics is the ability to support the whole process with only one line of code, that you only have to put in your app once. So you don’t have to preplan your tests before deploying your app.
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.
