Live data from Hacker News

Anatomy of My Kubernetes Cluster

ttt.io

31–38 of 38 posts

Re: Anatomy of My Kubernetes Cluster

#31

Real question coming from a non-k8-user. What would you use something like this for? Server hosting or?

I started playing with Elixir on mine, but installing Elixir on ARM is enough of a pain that I opted for a Docker image instead so I only had to build it once.

Re: Anatomy of My Kubernetes Cluster

#32
Wow it's really beautiful, looks like a real rack.

I wonder, the wires seems to be very hard to bend. When I built custom PC, there's custom build soft power supply / SATA wires for sale. Maybe there should be similar things for USB or other wires that could be easier to tuck in the case.

Re: Anatomy of My Kubernetes Cluster

#33

Wow it's really beautiful, looks like a real rack. I wonder, the wires seems to be very hard to bend. When I built custom PC, there's custom build soft power supply / SATA wires for sale. Maybe there should be similar things for USB or other wires that could be easier to tuck in the case.

Wonder what a setup using PiBlades might look like

http://www.bitscope.com/product/blade/?p=about

Re: Anatomy of My Kubernetes Cluster

#34

Real question coming from a non-k8-user. What would you use something like this for? Server hosting or?

If you're serious about messing around with your own k8s cluster, you're way better off just using virtualization. If you really want to run on your own hardware, grab an old laptop or desktop computer and KVM and have at it.

The Pis are just fun toys for people who enjoy tinkering with hardware. This kind of setup isn't really useful (or even educational in any kind of general way outside of the Pi specific details), but some people enjoy it.

Re: Anatomy of My Kubernetes Cluster

#35
post #21

Earlier quoted context omitted.

This seems to be a Kubernetes thing. Why the hell does it idle using 25% of my 4 CPUs?

That makes no sense. Try looking at logs and such at least.

The logs don't say much. It's mostly the API server getting hammered by nodes and various components.

Re: Anatomy of My Kubernetes Cluster

#36
post #35

Earlier quoted context omitted.

That makes no sense. Try looking at logs and such at least.

The logs don't say much. It's mostly the API server getting hammered by nodes and various components.

Ok so it's just the API servers. Not every node which is what it sounded like. Typically you wouldn't run normal workloads on the same host as the API. Although these quick "how I did it" articles have a tendency to skip best practice. Still sounds like something isn't right in your environment. They shouldn't be hammered that hard unless you have a very large cluster.

Re: Anatomy of My Kubernetes Cluster

#37

More software engineers should build Kubernetes clusters like this at home... So they don't have to do it at their work. (Unless they work at a large enough company to justify one.)

A $500 per person "get it out of your system at home" fund, I love it

$500 might be on the low side, but it would cover a good percentage of the cost. :)
Post reply on HN