Re:Google Kubernetes Engine is introducing a cluster managem...
by briangrant on Wednesday March 04, 2020 @05:26PM
(#22488824)
Re. managing GCP as Kubernetes resources:
https://cloud.google.com/config-connector/docs/overview
Re:Google Kubernetes Engine is introducing a cluster managem...
by atombender on Wednesday March 04, 2020 @05:34PM
(#22488902)
That's very cool, thanks! Note that this allows selectively creating Kubernetes resources backed by GCP resources. Looks like it will not automatically sync everything that already exists, which seems like a missed opportunity.
Re:Google Kubernetes Engine is introducing a cluster managem...
by praveenperera on Wednesday March 04, 2020 @04:52PM
(#22488553)
But DigitalOcean has managed K8s now: https://www.digitalocean.com/products/kubernetes/
Re:Google Kubernetes Engine is introducing a cluster managem...
by atombender on Wednesday March 04, 2020 @05:14PM
(#22488727)
DigitalOcean did not have Kubernetes then. Are you suggesting we should spend 6-12 man months migrating back?
Re:Google Kubernetes Engine is introducing a cluster managem...
by tie_ on Wednesday March 04, 2020 @05:46PM
(#22488989)
How about contracting an ops-oriented person for a month that would do the migration for you? Where do those cost functions intersect?
Re:Google Kubernetes Engine is introducing a cluster managem...
by atombender on Wednesday March 04, 2020 @05:54PM
(#22489043)
Would never happen. Just the amount of time needed to dedicate to onboarding a temporary contractor would be really disruptive to the developers, not to mention the disruptive effect of the technical migration — databases to move over, persistent volumes to copy, DNS to repoint, lots of downtime, etc. There's a good reason companies don't switch clouds often.
Re:Google Kubernetes Engine is introducing a cluster managem...
by tie_ on Wednesday March 04, 2020 @06:04PM
(#22489121)
If it takes more than a month to migrate a 20-node K8s cluster, then that's a red flag. Too much tech debt or a strong vendor lock-in? Either deserves attention.
Re:Google Kubernetes Engine is introducing a cluster managem...
by atombender on Wednesday March 04, 2020 @06:52PM
(#22489479)
Doing the migration might take a few late evenings; deploying all our apps and Helm charts to a new cluster takes just a few commands. Learning what needs to be migrated, deciding on how the configuration should look on the destination end of it, and designing a detailed plan and checklist for the whole process is the big task. Adding the onboarding of someone who's never seen the inside of your company and you're talking about a longer, more disruptive process. Tech debt isn't a factor here.
Re:Google Kubernetes Engine is introducing a cluster managem...
by praveenperera on Thursday March 05, 2020 @10:25AM
(#22494264)
> Learning what needs to be migrated, deciding on how the configuration should look on the destination end of it ...
Sounds like you've identified an area of risk you should address
Re:Google Kubernetes Engine is introducing a cluster managem...
by praveenperera on Wednesday March 04, 2020 @05:28PM
(#22488837)
No my mistake DOKS came out late 2018.
I had been using it since May 2018 but it didn't come out of early access till December.
We migrated our stuff from DigitalOcean around 2018. At the time, we briefly toyed with the notion of self-hosting Kubernetes on DO, but it's complex to manage, and we don't have any dedicated ops staff. GKE is significantly easier to manage.
At that time we migrated, the things you mentioned weren't available/mature, I think. Even today, I'd choose Kubernetes over a complex mishmash of different systems. I like the unified, extensible ops model. In fact, I'd go so far as to say that I wish all of GCP could be managed as Kubernetes objects.