4 ms·

The most important thing for me about Kubernetes is that it makes things fun again. (YMMV) The Kubernetes Slack is super friendly and helpful! (also YMMV ;) )

The most important thing for me about Kubernetes is that it makes things fun again. (YMMV) The Kubernetes Slack is super friendly and helpful! (also YMMV ;) ) The article is factually accurate and the mental model is consistent with other K8s docs, but I'm not sure I've seen it put so concisely from an outside perspective before. The ¹ footnote should have been in-line, because "front-loading" complexity is a great explanation: distributed systems are hard, and require a whole bunch of decisions. It's intimidating to be faced will all of those decisions up front, but at least they're all visible, and it forces you to be very clear on what you want, or you get nothing. I'd rather be surprised and confused (which is to say, have to think) now rather than in 6 months when I realize I had not accounted for some something. Finally ... I would be lost without k9s: https://k9scli.io/ https://k9scli.io/

throwaway9183T 5y ago
faeyanpiraat 5y ago
Have you run into any breaking issues with k9s, or is it stable for production use?
- evilduck 5y ago
  K9s is just a convenient interface to kubernetes, I've not done much with it in production but if anything were to happen I would just use the kubectl commands directly. It's like emacs magit vs git itself. And just like git GUIs, you should also learn the underlying tool first.
- p_l 5y ago
  Used it pretty heavily in previous job, especially given that our log shipping was... deficient is being nice about it. Thus k9s with log view on multiple containers while we were debugging something hairy (turned out to be a problem on clients end, not in our k8s cluster)
darkwater 5y ago
> The most important thing for me about Kubernetes is that it makes things fun again. Because you have to re-learn things you were already doing, new bugs and edge-cases to fix or waiting to be implemented etc etc. I understand the fun part to tinker with a new toy, but it cannot be the only parameter taken into account when making a decision.
nijave 5y ago
Not only k8s, but other CNCF and Kubernetes native software, too. Layer on fluentd/bit, Prometheus, etc and you can stand up a production ready compute platform with observability, monitoring, and alerting in a day.

throwaway9183T 5y ago

faeyanpiraat 5y ago

Have you run into any breaking issues with k9s, or is it stable for production use?

evilduck 5y ago
K9s is just a convenient interface to kubernetes, I've not done much with it in production but if anything were to happen I would just use the kubectl commands directly. It's like emacs magit vs git itself. And just like git GUIs, you should also learn the underlying tool first.
p_l 5y ago
Used it pretty heavily in previous job, especially given that our log shipping was... deficient is being nice about it. Thus k9s with log view on multiple containers while we were debugging something hairy (turned out to be a problem on clients end, not in our k8s cluster)

darkwater 5y ago

> The most important thing for me about Kubernetes is that it makes things fun again. Because you have to re-learn things you were already doing, new bugs and edge-cases to fix or waiting to be implemented etc etc. I understand the fun part to tinker with a new toy, but it cannot be the only parameter taken into account when making a decision.

nijave 5y ago

Not only k8s, but other CNCF and Kubernetes native software, too. Layer on fluentd/bit, Prometheus, etc and you can stand up a production ready compute platform with observability, monitoring, and alerting in a day.