Wait until people realize gcp might not exist after 2022 if it’s not profitable. Better pay for it than have your platform yanked out from under you.
Google Kubernetes Engine is introducing a cluster management fee on June 6
431–440 of 633 posts
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#432Earlier quoted context omitted.
Assuming you can do that, and your system is not using namespacing for its own purposes.
I know kubeflow can use namespaces for its own purposes, but otherwise I thought that was quite rare. Namespaces are intended to be used for exactly this usecase (isolating teams and/or workloads). What kind of system have you seen where this isn't true?
I use namespaces to isolate names. So I can have a service called memcached in namespace A and also one in namespace B.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#433This strikes me as an attribution problem e.g. Within large companies business units are treated as standalone financial entities so you are either making money or a cost center. I think what could be happening here is that the kubernetes group is generating what look like un-paid-for costs, instead of being back-credited for ALL of the compute they are selling via the worker VMs. I would argue that people come to GC…
[deleted]
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#434This is awful - I don’t think GCP is fully aware of their position in the market as the second, inferior choice. I took a bet on the underdog by using GCP and they bit me back in return. Especially considering their ‘default’ kubernetes config automatically sets you up with three(!) control planes in replication, that’s, as far as I understand, $~300 added to our monthly bill, for nothing. Oh, and per their docs, thr…
For what it's worth, we're seeing a GKE being the main reason prospective clients use GCP at Latacora, to a point where I'd say I was surprised if someone was on GCP but _not_ using GKE. Obviously that's a small subset of all companies, but GKE does seem like the goose that lays the golden eggs for them, at least insofar they care about startup market share. I also think of them as the second, inferior cloud, but the…
I've used both extensively, GKE is superior to EKS in every way... Except on cost it now seems.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#435Wait until people realize gcp might not exist after 2022 if it’s not profitable. Better pay for it than have your platform yanked out from under you.
Better still to take this opportunity to get out before Google does what Google does best.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#436Earlier quoted context omitted.
Disclaimer: I work for Red Hat and am very biased, but this is my own honest opinion. If you're going to run on bare-metal or in your own VMs, OpenShift is very much worth a look. There are hundreds, maybe thousands of ways to shoot yourself in the foot, and OpenShift puts up guard rails for you (which you can bypass if you want to). OpenShift 4 runs on top of RHCOS which makes node management much simpler, and allow…
Don't want to sound snarky, but how about an upgrade path from 3.11 to 4.x? I am a heavy Openshift user and it seems that RH just dumped whatever architecture they had with pre-4 clusters and switched to a Tectonic-like 4.x installations without any way to upgrade other than a new installation. This makes it hard to migrate with physical nodes.
There is a free tool to help with migrations from OpenShift 3.x to 4.x - https://access.redhat.com/documentation/en-us/openshift_cont...
It's not a rolling upgrade, but it allows you to move the apps, PVs, policies in as granular a manner as you wish.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#437Earlier quoted context omitted.
As also a security person (:wave:), you can use dedicated node pools and workload identity to isolate workloads in the same cluster.
Workload identity is a GCP-specific beta feature for mapping to GCP IAM, right?
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#438Earlier quoted context omitted.
Hi Seth, What about clusters that are used for lumpy work loads? Like data science pipelines? For example, our org has a few dozen clusters being used like that. Each pipeline gets its own cluster instance as a way to enforce rough and ready isolation. Most of the times the clusters sit unused. To keep them alive we keep a small, cheap, preemptive node alive on the idle cluster. When a new batch of data comes in, we…
On GKE, you can use a single cluster with multiple node pools to achieve a similar effect. Just set the right affinity on your job resources.
PTAL at doing Multi-Tenancy in GKE!
https://cloud.google.com/kubernetes-engine/docs/best-practic...
We don't recommend using node pools for isolation.
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#439What’s the betting line on GCP shutdown? Q3 2021? Q2?
Re: Google Kubernetes Engine is introducing a cluster management fee on June 6
#440Earlier quoted context omitted.
On GKE, you can use a single cluster with multiple node pools to achieve a similar effect. Just set the right affinity on your job resources.
PTAL at doing Multi-Tenancy in GKE! https://cloud.google.com/kubernetes-engine/docs/best-practic... We don't recommend using node pools for isolation.
That guide looks nice. Have you guys thought about releasing a terraform module or even a cloud composer workflow that will set that up in a project?