HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kelseyhightower
kubernetes-the-hard-way
Systems & Infrastructure2016–2025
kelseyhightower / kubernetes-the-hard-way

kubernetes-the-hard-way

Bootstrap Kubernetes the hard way. No scripts.

63Distinct people
67Mentions
0Explicit recommenders
50.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Bootstrap Kubernetes the hard way. No scripts.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year67 dated mentions

Observed mentions: 2016-07-08 11:07:08 UTC to 2025-04-16 22:42:31 UTC.

051015202016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 18 mentions; 8 submissions, 10 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC18810
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC11110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC835
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC514
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC826
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC431
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

11 sources
I am not sure if I can. Setting it up by scratch let me become familiar with some of the underlying mechanisms of how k8s is put together. A part of that is: https://rocketeer.be/blog/2015/11/kubernetes-from-the-ground... And although I never ran through Hightower's Kubernetes the Hard Way, it is like that. https://github.com/kelseyhightower/kubernetes-the-hard-way After running through that as a kind of kata, it was easier to infer and troubleshoot things when things go wrong. The transfer-of-learning happens only if you run yourself through these exercises. I can share some things at a higher level though: Label selectors are your friend. Master them. They are used everywhere. Stateless is still easier than stateful. Start with putting stateless workloads in production before ever trying stateful. If you have the expertise to mix your s
Read the rest
tateful pods with your stateless pods, make sure you master StatefulSet and things like persistant volume claims. If you fake stateful pods like I did in production, then Kubernetes does not know how to cleanly shut them down. Automated maintenance involving kubectl cordon and drain no longer function well. You end up having to hand migrate stateful pods from node to node.
In Adding Kubernetes support to the Docker platform
When my team was learning about Kubernetes we worked through Kelsey Hightower's "Kubernetes the Hard Way": https://github.com/kelseyhightower/kubernetes-the-hard-way Obviously this much more complicated that using a tool such as kubeadm to deploy Kubernetes however it gives you a really good understanding of how a Kubernetes cluster is put together. One of my colleagues used the experience from working through this with a set of VMs to create a tool called kubicle: https://ciao-project.github.io/kubicle.html This allows you to build a Kubernetes cluster on your own physical machines by building it on top of a Ciao cluster if you're not able to use public cloud hosted VMs. For learning you can combine this with Ciao's "singlevm"/ccloudvm mode to run a cluster inside a VM (with nested VMs.) Full disclosure: I currently work on the Ciao team
Read the rest
@ Intel :-)
In Ask HN: Are you learning Kubernetes/Docker? What resources are you using?
I myself don't publish but I've seen some authors use Markdown and [1] GitBooks. Kelsey Hightower wrote Kubernetes: The Hard Way in the same manner [2]. It reads nicely. For publishing, you could look into GumRoad [3]. When I do some technical writing, I personally like to use StackedIt which supports Markdown and allows you to export to PDF with custom layouts. [1] https://www.gitbook.com [2] https://github.com/kelseyhightower/kubernetes-the-hard-way [3] https://gumroad.com [4] https://stackedit.io
In Ask HN: How do you author your eBooks in 2017?
Is it me, or does it seem weird to encrypt your secrets by uploading the secret key to GCP (contained in the config .yaml file)? I assume the controller instances are operated by Google in this[1] example. Moreover, is there any sensible way at all to encrypt secrets without baking the secret key into your image? I can’t think of any. I want to deploy an app that makes use of one or more fairly important secrets, but I haven’t found a sensible way to make it auto-scale while keeping the secrets on-premise. As far as I can see, the only sensible solution is to create in-cloud/off-premise secret keys that can only be accessed by images signed with an on-premise secret key. So, 1. Create secret key on an offline, on-premise machine 2. Produce application image, transfer to offline machine, sign with on-premise secret key 3. Create off-premis
Read the rest
e (in-cloud) secret, which can only be accessed by images signed with the on-premise secret key 4. Upload app image and signature to the cloud, allowing only this image access to the in-cloud secret [1] https://github.com/kelseyhightower/kubernetes-the-hard-way/b...
In Bootstrapping Kubernetes Google Cloud Platform without scripts
If you want to get started with Kubernetes I'd recommend either, Kelsey Hightower's Kubernetes the hard way (https://github.com/kelseyhightower/kubernetes-the-hard-way) which is a good way to start getting an understanding of the various components and how they fit together or, if you want to try out running workloads on a cluster, Kubeadm (https://kubernetes.io/docs/setup/independent/create-cluster-...) If you're interested in books on the topic, I like Kubernetes in Action (https://www.manning.com/books/kubernetes-in-action) or Kubernetes: Up and running (http://shop.oreilly.com/product/0636920043874.do) One of the challenges with Kubernetes is that it's pretty fast moving, so it's a good idea to work with resources that are up to date. I know a last commit from May doesn't seem very old but that's going to a least be missing 1.7 and co
Read the rest
uld be missing 1.6 or earlier as well.
In Kubermesh: self-hosted/healing/provisioning, partial-mesh network K8s cluster
Specifically in reply to your messages, but also relevant to any others replying to you or not having done enough DA research: False. I can relate albeit not having that kind of attention, but had my current manager continually try to hire me for months and get me to interview (which I don't go out of my way saying either because it doesn't make sense to and I want others to think well of me because of my skills--which they often think higher of than I do myself) and she is much more knowledgeable and regarded in the community than me so I am not remotely surprised she was contacted so much and I know for fact that these daily calls DID happen--the ONLY reason she mentioned it was to explain why the process moved so quickly--not so she can go pat herself on the back because she is humble. Maybe you should go look her up on Twitter. She di
Read the rest
dn't amass a ton of followers for PR/marketing fluff. She's well known in the community due to the contributions she has made and has done a lot of great TECHNICAL things to help people learn e.g. https://github.com/ashleymcnamara/learn_to_code Developer advocate is a widely used term and you can't assume a general definition. I am a developer advocate myself and part of my role is being a software engineer--I am in an engineering org, report to an engineering manager, and this means I code ON the project just like every other software engineer here, just not as my entire role. The difference is I also speak at conferences, make blogs/training material so that people in the community can learn more about how to use the product(s) (not market fluff). Whether it's coding on their team's project(s), coding on external open source software, or creating demo code, MANY developer advocates are partaking in the technical side themselves and they have to be very knowledgeable to be able to write the technical content in blogs independent of whether it's something they created or not. You realize this is a post about why she joined, not a general thoughts on the company or a technical overview, right? Therefore it will be the positive things. Also, it can't be just technical merits when you are deciding to join a company. It takes interesting topics and good engineering of course, but also great managers, great team members, a vision, what you'll be working on, etc. She wrote this to explain to people why she switched to Microsoft, not as anything to do with her job. I, and I am sure others, would appreciate it if you would please get off your high horse and go study up more on facts before you partake in condescending activity yourself by shitting on/slamming someone for something you haven't researched enough on. In this case it could include asking more of "what will you be doing?". And in general, it is best to avoid those types of things in general. Maybe give some technical feedback to posts instead with useful feedback/how to improve things and not dumping on it independent whether you agree with it or not. Also, go look at some talks/blogs etc from Developer Advocates (and similar titles like Technical Evangelist, Principal Technologist) in the community that include plenty of technical (vs marketing) content and help people learn such as: Francesc Campoy https://twitter.com/francesc at Google https://github.com/campoy/go-tooling-workshop Abby Fuller https://twitter.com/abbyfuller at Amazon Web Services https://github.com/abby-fuller/ecs-demo Scott Hanselman https://twitter.com/shanselman at Microsoft https://www.hanselman.com/blog/ Arun Gupta https://twitter.com/arungupta at Amazon Web Services Julia Ferraioli https://twitter.com/juliaferraioli at Google (formerly a DA) http://blog.juliaferraioli.com/2015/11/containerized-minecra... Kelsey Hightower https://twitter.com/kelseyhightower at Google https://github.com/kelseyhightower/kubernetes-the-hard-way And many others.
In Why I joined Microsoft
Because Kubernetes is a complex beast with many moving parts, and learning about all those moving parts becomes more and more important as your usage grows. Personally I've used Stackpoint.io to provision some small clusters but I was very excited to see this project because deploying my own cluster from scratch is next on my todo list. Kelsey Hightower's "Kubernetes the Hard Way"[1] is the canonical go-to reference here but it's also very daunting so this looks like a great middle ground. Let's face it, even today the k8s docs can be quite sparse sometimes or gloss over the details, so knowing how all of the pieces work from the ground up can be a big help. Plus, you prevent vendor lock-in when whatever automated tool you're using doesn't solve your use-case or decides to start charging a lot of money. [1] https://github.com/kelseyhighto
Read the rest
In Kubernetes clusters for the hobbyist
I'm actually right in the middle of putting that together as well. I quickly arrived at analysis paralysis when choosing how to bootstrap Kubernetes and run it in production given the tremendous flexibility. Tons of options[1], but nearly all of them are incompletely documented. Ended up walking through Kelsey Hightower's K8s the hard way[2] repo to peel it all apart. End result will probably look something like Terraform -> SaltStack -> Kubernetes. [1] https://kubernetes.io/docs/getting-started-guides/ [2] https://github.com/kelseyhightower/kubernetes-the-hard-way
In The Basics: Kubernetes, Mesosphere, and Docker Swarm

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.