4 ms·

(Disclaimer: I have never used k8s, so cannot assess the factual accuracy of this piece.) If Kubernetes hasn’t yet incorporated this article into their documen

(Disclaimer: I have never used k8s, so cannot assess the factual accuracy of this piece.) If Kubernetes hasn’t yet incorporated this article into their documentation somewhere prominent, they should. This is an excellent, and crucial, piece of documentation: providing a mental model and explaining key design decisions. All complex systems should have a document like this one. As a newcomer, this is what I want to read first. Bravo, author. I hope you get rewarded.

thundergolfer 5y ago
The article is only a few hours old, so K8s devs would have to be very quick on the uptake to have it incorporated. But agree that it provides a great mental mode for K8s
pid-1 5y ago
I would add one more thing: K8s is complex because oci containers are complex. Running a process in isolation in Linux means dealing with many different, resource specific APIs. Unfortunately, any Linux container orchestrator will inherit the resulting complexity.
- motoboi 5y ago
  Actually running the container is a small part of kubernetes.
  - waynesonfire 5y ago
    Agree, this is abundently clear when attempting to get similar value on a freebsd system using jails.
- randomswede 5y ago
  Kubernetes is complex because coordinating potentially hundreds och machines with potentially tens of thousands of containers so that it all flows smoothly, expediently, and allows change is a complex problem.
thanatos519 5y ago
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

thundergolfer 5y ago

The article is only a few hours old, so K8s devs would have to be very quick on the uptake to have it incorporated. But agree that it provides a great mental mode for K8s

pid-1 5y ago

I would add one more thing: K8s is complex because oci containers are complex. Running a process in isolation in Linux means dealing with many different, resource specific APIs. Unfortunately, any Linux container orchestrator will inherit the resulting complexity.

motoboi 5y ago
Actually running the container is a small part of kubernetes.
- waynesonfire 5y ago
  Agree, this is abundently clear when attempting to get similar value on a freebsd system using jails.
randomswede 5y ago
Kubernetes is complex because coordinating potentially hundreds och machines with potentially tens of thousands of containers so that it all flows smoothly, expediently, and allows change is a complex problem.

thanatos519 5y ago

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