Kubernetes from the ground up: the API server

Re:Kubernetes from the ground up: the API server by kalmar on Sunday September 06, 2015 @09:01PM (#10179697)

My main resource is probably time. I read all the documentation when Kubernetes was first announced, and reread it when they were coming up to 1.0. I've also been following the proposals and issues a little. I've also got a clone of the codebase and read bits to make sure I'm understanding what goes on.

But yeah, it's a really fast moving project with a lot of moving parts, and I'm still not on top of everything!

[ Parent | on HN ]

Re:Kubernetes from the ground up: the API server by AndrewHampton on Sunday September 06, 2015 @09:09PM (#10179712)

Thanks for the info! I've found the end user documentation to be excellent, but the documentation for actually managing a cluster to be lack luster. This series has been perfect for filling in that gap. Thanks again!

[ Parent | on HN ]

Re:Kubernetes from the ground up: the API server by TheIronYuppie on Monday September 07, 2015 @12:17AM (#10180041)

Disclaimer: I work at Google on Kubernetes

I'd love if you could mention stuff in particular that you felt like was missing - we're trying hard to catch up!

[ Parent | on HN ]

Re:Kubernetes from the ground up: the API server by mkulke on Monday September 07, 2015 @03:07AM (#10180404)

Specifically some canonical instructions on how to harden a cluster would be helpful. Many Starting Guides have nodes use plain http to talk to the api server, thus even deployed containers can do this do.

It took me a while to find a proper kubeconfig example for kubelet and kube-proxy token auth (the one I eventually found was buried in some github issue i think).

Also, I found no information on how on what to put in the authorization jsonl file for kubelet (the given example is wrong, since the kubelet needs to write/report node status to the api) and kube-proxy. Peeking into the code helped, but I guess this information could be helpful for admins.

[ Parent | on HN ]