> By its nature, K8s is designed to host stateless apps. It is fantastic at doing this, to be clear. I love K8s. But a system where the nodes can (and should, if you're taking advantage of spot pricing) disappear with a few minutes' warning is not a great host for an RDBMS.
Why is this a problem? A typical deployment will have multiple replicas, with (hopefully) small replication lag. Those should be able to be promoted to be the new primary within a minute.
Cloudflare | Senior/Staff Systems engineer – database platform | Remote | UK, Germany, Portugal or Netherlands
We are hiring a systems engineer at Cloudflare. Our team is responsible for managing all of Cloudflare's internal Postgres deployments. This particular role fullstack engineer-ish since this will involve writing frontend code for a system that engineers use to interact with databases, among other things.
I am not the hiring manager but I am a part of this team, happy to answer any questions.
No, but there might still be basis for a lawsuit. For example, if a worker can prove that they need to be remote due to a medical condition, that might make this discrimination on that medical condition.