3 ms·
I'm not sure what the logic here is compared to AWS Outposts and Azure Stack. AWS Outposts and Azure stack support a very large number of Azure services and Ant
by _jezell_ 8y ago
I'm not sure what the logic here is compared to AWS Outposts and Azure Stack. AWS Outposts and Azure stack support a very large number of Azure services and Anthos just supports GKE and Istio? So there's no first class story for basic things like queues and blob storage? How many people really use Kubernetes without needing a persistent volume claim?
I like the idea of something you can just install and run on your existing hardware, but that doesn't seem to be the goal of this either as they only support a single router and a single proprietary virtualization platform. That seems even worse than just giving you a box you can plug in like AWS and Azure.
Bigger question is what is it going to take for Google to offer anything more than this? Google has very restrictive source code policies internally, so I'd guess they'd be extremely reluctant to let the binaries for things like BigTable which run all of Google and GCP leave their network. Do they rewrite all their services or let BigTable run outside of firewall and throw an atomic clock in the box?
- cavisne 8y agoThe same limitations apply to the other on prem services. Theres no way the real EBS control and data plane is running on prem, its just some compatible service. Outposts has a limited feature set if you arent using vsphere, and Azure uses Microsoft's existing private cloud/on prem stack. Enterprises are scared of one way bad decisions so if GC can convince them containerizing and moving their apps to kubernetes first is worth it over "lift and shift" this could go well. One of the few competitive advantages google has for enterprises is they can point to Amazon and Azure being forced to add managed Kubernetes services, because customers wanted that instead of a proprietary orchestrator.