> Can you honestly say it would be a complete surprise, however, if Google announced an EOL for GCP?

All of GCP? That would surprise me. Any particular GCP offering I may depend on that they decided to deprecate or replace? Absolutely.

> Can you honestly say it would be a complete surprise, however, if Google announced an EOL for GCP?

Of course. Anyone who thinks otherwise has just bought into a virulent meme and isn't actually thinking.

Yes. I can honestly say this would be extremely surprising given the tenants, and the rate of change of the core kubernetes model. I do not believe the dead products list typically has either this paying customer base, or code change.

Who are the notable GCP tenants? Just curious.

Tbh, the only reason I use GCP is Firebase, and the only reason I use Firebase is because it's usable for my (limited) purposes in a neat format. I'm currently in the process of migrating some functions to AWS, but it's so clunky, almost 2005-esque.

Even if they did, for such a big service there would be a long transition period. E.g. 2 years, so you could move somewhere else.

That assumes that you can move off the system and that’s enough notice. Not to mention that it blows up your roadmap.

What’s the point of outsourcing heavy lifting if the vendor is just going to surprise drop it back on your at an in opportune time?

That would be reasonable, yes. But not expected from Google.

Wow, 2 years, such a long time

Yeah, I mean, I get their huge history shutting down small ancillary projects that they didn't see as strategic advantages, but GCP isn't one of those, and probably not for the foreseeable future.

Wave wasnt small ancillary, Google+ wasnt small ancillary. Google Hangouts wasnt small ancillary, reader wasnt small ancillary.

By that bar GCP is in the same boat. Good luck with that!

Wave was, Google+ failed, Hangouts got merged into Duo or whatever they call it now, Reader was.