6 ms·
This particular problem you mentioned can easily be solved in ways that do not involve Kubernetes, for example, having a linux image w/ prometheus daemon runnin
by aprdm 6y ago
This particular problem you mentioned can easily be solved in ways that do not involve Kubernetes, for example, having a linux image w/ prometheus daemon running and some sort of service discovery (consul) that prometheus hooks to to discover the infrastructure.
- rektide 6y agoKubernetes is more all encompassing than the alternatives. I see no incentive to go about cobblimg together specific tools to get one capability, when I can start using a much more powerful consistent cloud architecture to manage my everything.
- aprdm 6y agoI have preferred smaller tools that do one thing only and are easy to manage / break in predictable ways.
- rektide 6y agoAn opinion we see thoroughly, adamantly expressed throughout the comments on this posting. Everyone seems very opposed. It seems odd to me, because Kubernetes is so new, and there have been few attempts to manage things consistently & well, under one umbrella, that have happened. Certainly none have gotten anywhere near this successful. I think there's a lot of value to trying to find core abstractions & use them throughout. Managing each resource via totally separate tooling is how we've always done things from an ops perspective, but the coders have been trying to distill & create enduring shareable value for a long time, find ways to share value. It's weird to me how resistant, how much people think they know what their opinion is, how certain they are that only small specific tools can help them, and how convinced they are that bigger attempts are going to be hard to manage, or convinced that they won't be able to see or understand breakage. I don't think we have the experience to know, yet people seem deeply committed already.