Re:Pitfalls of Helm – Insights from 3 yrs with the leading K...
by jen20 on Thursday December 14, 2023 @12:01PM
(#38643700)
If you run a multi-tenant Kubernetes cluster at scale, operators with poor discipline spamming the API servers and taking etcd down is a leading cause of sadness.
Re:Pitfalls of Helm – Insights from 3 yrs with the leading K...
by morelisp on Thursday December 14, 2023 @12:13PM
(#38643898)
This is the common view among our ops team, sure, but for a vocation so prima facie obsessed with postmortems/five-whys/root-causes/etc it's depressingly shallow.
Re:Pitfalls of Helm – Insights from 3 yrs with the leading K...
by cassianoleal on Thursday December 14, 2023 @01:39PM
(#38645230)
Generally speaking, operators and CRDs are more in the domain of your platform rather than your products. They should provide common interfaces to implement the business requirements around things like uptime, HA, healthchecking, observability, etc.
If a product team sees itself needing to deploy an operator, it's likely the platform is subpar and should be improved, or the product team is overengineering something and could do with rethinking their approach.
As in most cases, a conversation with your platform/ops/devops/sre/infra team should help clarify things.
Maybe it's just us, but our operations team puts pretty hard restrictions on how we're allowed to talk to the K8s API directly. We can turn a regular Deployment around as fast as we can write it, but if we needed a controller and CRD update it'd take us like three days minimum. (Which, I even sort of understand because I see the absolute garbage code in some of the operators the other teams are asking them to deploy...)