https://github.com/geerlingguy/youtube-10k-pods

10,000 Kubernetes Pods for 10,000 Subscribers
https://github.com/geerlingguy/youtube-10k-pods

ansible aws celebration eks k3s kubernetes subscribers youtube

Last synced: 16 days ago
JSON representation

10,000 Kubernetes Pods for 10,000 Subscribers

• Host: GitHub
• URL: https://github.com/geerlingguy/youtube-10k-pods
• Owner: geerlingguy
• Created: 2020-05-15T19:51:05.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-05-15T23:35:42.000Z (over 4 years ago)
• Last Synced: 2024-10-10T04:06:45.153Z (about 1 month ago)
• Topics: ansible, aws, celebration, eks, k3s, kubernetes, subscribers, youtube
• Homepage: https://www.jeffgeerling.com/blog/2020/10000-kubernetes-pods-10000-subscribers
• Size: 10.7 KB
• Stars: 77
• Watchers: 6
• Forks: 25
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml

Awesome Lists containing this project

README

        
# 10,000 Kubernetes Pods for 10,000 Subscribers



> **tl;dr**: See the blog post that accompanies this project: [10,000 Kubernetes Pods for 10,000 Subscribers](https://www.jeffgeerling.com/blog/2020/10000-kubernetes-pods-10000-subscribers).

This repository contains automation to build a large Kubernetes cluster in AWS, and run 10,000 Pods on that cluster. And it does it two ways, because I realized that the first way didn't work without running 1,000 vCPUs in my brand new AWS account (AWS support usually doesn't look kindly on people who open a new account and immediately ask for insane capacity increases!).

  - [`attempt-one-eks`](attempt-one-eks/) is the first attempt: build an EKS cluster with 100 `t3.micro` nodes; later updated to use 14 `m5.16xlarge` nodes, which worked but required an insane amount of computing power, which would cost over $30,000/month!

  - [`attempt-two-k3s`](attempt-two-k3s/) is the second attempt: build a K3s cluster with one `c5.2xlarge` master and 100 `c5.large` nodes. (I almost got it working with `t3.micro` nodes but they started dying when I deployed 100 Pods to each node...).

In the end, I found out that burstable `t3` instances just aren't ready for massive amounts of pods, no matter what. I run into networking _and_ burst CPU limits. And EKS has some annoying limitations with it's current VPC CNI networking, but those could be overcome if you take the time to swap out a different networking solution.

If you're interested in automating Kubernetes with Ansible, I have the _perfect_ book for you: [Ansible for Kubernetes](https://www.ansibleforkubernetes.com).