4 ms·

Another fairly happy GCP user. They have their issues (everyone does), but GKE is pretty amazing if you don’t have the resources for an in house k8s on AWS team

by pm90 7y ago

Another fairly happy GCP user. They have their issues (everyone does), but GKE is pretty amazing if you don’t have the resources for an in house k8s on AWS team. I am however fairly pessimistic about their chances. Especially considering the person at the helm is ex-Oracle VP. I also don’t understand their alternatives... do they want AWS to own the cloud market? They’ve operated Android as the bulwark against Apple, why not view GCP in a similar light?

dehrmann 7y ago
> They’ve operated Android as the bulwark against Apple, why not view GCP in a similar light? Android has a lot more synergies with their consumer ads business. It's the extreme version of writing your own browser. GCP is completely different; it's in the B2B space, and it's a pretty standard business relationship between businesses and a supplier. Being customer-focused and business-focused isn't in Google's DNA.
ForHackernews 7y ago
How is GKE different/better than Amazon's EKS? Am I wrong to think that 'hosted k8s' is an interchangeable commodity product?
- inscrutable 7y ago
  On GKE, you don't need to define node-pools if you tick enable node-autoprovisioning. This is effectively an EKS fargate profile without any of the limitations (discrete node size, inability to mount volumes etc) On GKE there's no need for bastion hosts, you can connect to private nodes automatically by tunneling through identity-aware-proxy On GKE, there's no faffing about with aws-auth-configmap, nodes automatically join the cluster On GKE, you can use regional persistent disks if you need to store state rather than single zone EBS On GKE, you can use a single static ip for your nginx-ingress load balancer without needing to faff about with AWS global accelerator (which in any case gives you multiple ips) On GKE, managed node pools are automatically repaired and upgraded with the choice of google's OS or ubuntu unlike Amazon Linux which is currently the only choice for EKS' managed node pools. GKE can automatically use spot instances unlike the farce on AWS with a 3rd party (spotinst) charging a premium for the same functionality On GKE, managed istio is ticking a box versus a self-install on EKS On GKE you need to worry much less about ip exhaustion as they use alias ips vs dedicated ENIs for EKS Associating IAMs with kuberenetes service accounts is much easier with GKE workload identity than with EKS' oidc webhook GKE has several features which EKS doesn't (calico, vertical pod autoscaling, binary authorisation, export of cluster data to bigquery) https://www.reddit.com/r/googlecloud/comments/ejxxn5/has_anyone_done_a_thorough_diff_analysis_between/fd47cda?utm_source=share&utm_medium=web2x https://www.reddit.com/r/googlecloud/comments/ejxxn5/has_any...

by pm90 7y ago

dehrmann 7y ago

> They’ve operated Android as the bulwark against Apple, why not view GCP in a similar light? Android has a lot more synergies with their consumer ads business. It's the extreme version of writing your own browser. GCP is completely different; it's in the B2B space, and it's a pretty standard business relationship between businesses and a supplier. Being customer-focused and business-focused isn't in Google's DNA.

ForHackernews 7y ago

How is GKE different/better than Amazon's EKS? Am I wrong to think that 'hosted k8s' is an interchangeable commodity product?

inscrutable 7y ago
On GKE, you don't need to define node-pools if you tick enable node-autoprovisioning. This is effectively an EKS fargate profile without any of the limitations (discrete node size, inability to mount volumes etc) On GKE there's no need for bastion hosts, you can connect to private nodes automatically by tunneling through identity-aware-proxy On GKE, there's no faffing about with aws-auth-configmap, nodes automatically join the cluster On GKE, you can use regional persistent disks if you need to store state rather than single zone EBS On GKE, you can use a single static ip for your nginx-ingress load balancer without needing to faff about with AWS global accelerator (which in any case gives you multiple ips) On GKE, managed node pools are automatically repaired and upgraded with the choice of google's OS or ubuntu unlike Amazon Linux which is currently the only choice for EKS' managed node pools. GKE can automatically use spot instances unlike the farce on AWS with a 3rd party (spotinst) charging a premium for the same functionality On GKE, managed istio is ticking a box versus a self-install on EKS On GKE you need to worry much less about ip exhaustion as they use alias ips vs dedicated ENIs for EKS Associating IAMs with kuberenetes service accounts is much easier with GKE workload identity than with EKS' oidc webhook GKE has several features which EKS doesn't (calico, vertical pod autoscaling, binary authorisation, export of cluster data to bigquery) https://www.reddit.com/r/googlecloud/comments/ejxxn5/has_anyone_done_a_thorough_diff_analysis_between/fd47cda?utm_source=share&utm_medium=web2x https://www.reddit.com/r/googlecloud/comments/ejxxn5/has_any...