4 ms·

Kubernetes Solves Its Biggest Problem: Managing Databases

• richwater 1y ago
  This article reeks of AI generation
  • kassner 1y ago
    I’d say more of a copy-paste from a different website. Most of the code blocks have a “CopyEdit” on line 2.
  • daveguy 1y ago
    I found it way more coherent, succinct, insightful, and well organized than the vast majority of slop that comes out of an LLM.
• Flux159 1y ago
  I'm not sure I would say this is solved - having used CNPG with GKE, I ended up moving off of hosting Postgres inside of Kubernetes & moving to Cloud SQL and Spanner for storing state in my apps. Few issues I found was that having stateful sets caused GKE to be unable to automatically update in my cluster setup. I had a read-write and read replica for a few postgres databases & the operator wasn't consistent with what pod id was read-writeable (you were able to retrieve this info from metadata though, so could script around it). Then having to setup backups to GCS manually & needing to ensure that they would work correctly to restore - easier to just pay GCP to deal with all of this with Cloud SQL.
• ghc 1y ago
  What is this, AI slop? Kubernetes operators have been around for ages. Heck, the OReilly book on them (https://www.amazon.com/Kubernetes-Operators-Automating-Container-Orchestration/dp/1492048046 https://www.amazon.com/Kubernetes-Operators-Automating-Conta...) was published in 2020.
• michalion 1y ago
  The tone of the article makes is sound like an ad. Not to mention promoting your own product.