2 ms·
> The problem with most black-box declarative interfaces is that you often do care about how things will happen. The real-world limitations often leak through t
by andrewjl 5y ago
> The problem with most black-box declarative interfaces is that you often do care about how things will happen. The real-world limitations often leak through the declarative interface, because you have to care about things like performance, or do things that don't quite fit into the opinionated declarative interface, or have other weird constraints that the authors didn't think of.
Can you give an example of this for k8s?
- morelisp 5y ago> Can you give an example of this for k8s? Deployment.spec.strategy is a common purely "how" configuration switch. Explicit PodDisruptionBudget is less common but exists only to configure a "how". A smarter (e.g. layer 6+ aware) system should be able to derive this for me. You might respond "well, that's what an operator is for" and in some sense you're correct, but every operator I've read is a mess of the most imperative code I've ever seen; and then that leaks out as soon as the operator's defaults don't work well for your case.