Add another smaller 2i2c federation member + k3s docs #3197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I wanted to understand what it would take to run a federation member on a small machine that does *not* have object storage nearby (I'm trying to get some new members where this is true). I also wanted to run through adding a new k3s member one more time so I can document it appropriately Sooooooo I bought a small server (16 cores AMD Ryzen with 64G of RAM and 1TB RAID1 SSD) via the wonderful [hetzner auction](https://www.hetzner.com/sb/) system. They sell older systems that are decomissioned from 'production' users but those are perfect for us. This costs 2i2c approximately 60$ a month in costs. If the server dies (because this is a physical object that has physical faults), we can just stop paying for it or try to ressurect it as we wish. I installed Ubuntu 24.04 and ran through k3s setup again, documenting every step I did! This helps future people joining the federation this way. Since this is in the same datacenter as the regular bigger 2i2c federation member, we can reuse the same object store backend for the registry! I can experiment with using filesystem for the registry in a future separate commit. I've added this to the federation with a 5% weight so it gets a little traffic but not much. Thanks to 2i2c for sponsoring this!
for more information, see https://pre-commit.ci
yuvipanda
added a commit
to yuvipanda/mybinder.org-deploy
that referenced
this pull request
Jan 25, 2025
Forgot to include these in jupyterhub#3197
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Forgot to add some files in this, added as #3198
I wanted to understand what it would take to run a federation member on a small machine that does not have object storage nearby (I'm trying to get some new members where this is true). I also wanted to run through adding a new k3s member one more time so I can document it appropriately
Sooooooo I bought a small server (16 cores AMD Ryzen with 64G of RAM and 1TB RAID1 SSD) via the wonderful hetzner auction system. They sell older systems that are decomissioned from 'production' users but those are perfect for us. This costs 2i2c approximately 60$ a month in costs. If the server dies (because this is a physical object that has physical faults), we can just stop paying for it or try to ressurect it as we wish.
I installed Ubuntu 24.04 and ran through k3s setup again, documenting every step I did! This helps future people joining the federation this way.
Since this is in the same datacenter as the regular bigger 2i2c federation member, we can reuse the same object store backend for the registry! I can experiment with using filesystem for the registry in a future separate commit.
I've added this to the federation with a 5% weight so it gets a little traffic but not much.
Thanks to 2i2c for sponsoring this!