piku
awesome-home-kubernetes
DISCONTINUED
Our great sponsors
piku | awesome-home-kubernetes | |
---|---|---|
26 | 16 | |
2,464 | 1,205 | |
2.4% | - | |
5.7 | 7.7 | |
3 months ago | over 1 year ago | |
Python | Python | |
MIT License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
piku
-
Show HN: Hancho – A simple and pleasant build system in ~500 lines of Python
I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)
-
Gokrazy Is Cool
I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).
Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.
I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).
(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)
-
Show HN: Local development with .local domains and HTTPS
I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814
-
Tool to deploy docker images from github repos?
Piku https://github.com/piku/piku
-
Stupid question: Why not use 'baremetal' OS instead of docker containers to run web apps?
So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.
-
Selfhosted PaaS? (No dokku pls)
piku?
- How do you deploy your side-projects?
- Ask HN: What's Your Proudest Hack?
-
Comparing selfhosted Heroku alternatives
Piku https://github.com/piku/piku
-
Zamjena za heroku
piku (nisam ga istraživao ali se pojavljuje tu i tamo)
awesome-home-kubernetes
-
A 4+1 node storage cluster intended for AI ingest datasets. What platform should we use? (ceph, btrfs, OpenZFS, TruNas Scale?
Also check out the awesome kubernetes@home repo where many homelabbers share their configs.
-
Running Kubernetes cluster locally to self host a bunch of applications along with a DNS server
Sorry I'm not familiar with this. Are you referring to this?
-
to kube or not to kube?
https://github.com/k8s-at-home/awesome-home-kubernetes https://github.com/k8s-at-home/template-cluster-k3s
- I must announce the immediate end of service of SSLPing
-
Deploy a Kubernetes cluster and have it automated from a Git repository!
To see it in action be sure to check out my repository or the many others here.
-
[github] k3s-io/k3s: Production ready, easy to install, half the memory, all in a binary less than 100 MB
Make it usable and link to the best place with k3s in action: https://github.com/k8s-at-home/awesome-home-kubernetes
-
Kubernetes best practices generally and for organizing my stuff
Check out Flux V2. It syncs a git repo with your cluster, allowing you to define your infrastructure as code. It will keep your cluster synced with your repo and detect changes. A number of example repos are Here and onedr0p did a example repo here There's many options for structuring folder, I'd recommend you have a look at a few repos and pick one you like. The linked template is a good start, as it helps avoid dependency hell with a crd folder that starts before the YAML that needs the crd defined. Many people on the awesome list also run ansible for full infrastructure as code. I spent a lot of time perfecting my setup to go from blank Ubuntu VM to my cluster with a few keystrokes. Running it in git also helps you be able to use things like renovate bot to keep versions up to date. As for namespaces, everyone had their own method, but about using kube-system. Also, keep a eye out for services that refuse to have their name space changed.
-
How did you really master Kubernetes?
This is more of less the exact path I took when diving in. I usually like to dog food anything I'm planning to use professionally and what helped alot was attempting to port my home stuff over to the k8s world. I use to have home assistant running in my house on a single RPI and it's evolved into a SOPS managed k8s cluster of NUCs easily deployable and git tracked. +1 on skipping helm charts initially, you add time but you learn alot more about what's going on under the hood manually piecing those deployments initially. One important thing is also considering upgrade strategies of all the things. Once you put something in the wild and it's used by others, that can quickly become a PITA. I'd recommend at some point in the investigation checking out https://github.com/k8s-at-home/awesome-home-kubernetes too, which is a great (awesome?) list of git ops managed k8s clusters in their community. They recently released a template that will let you bootstrap a k3s cluster tied it to a git repo that lets to leverage simple CI to action deployments to your cluster.
-
Created a k3s cluster server with Raspberry Pis, What is next?
Take a look at https://github.com/k8s-at-home/awesome-home-kubernetes for ideas, https://github.com/k8s-at-home/charts for some "home" focused helm charts, and https://discord.gg/Yv2gzFy for any help with the charts or running k8s-at-home.
-
The Decline of Heroku
huge fan of k8s. drop what you're doing & use a cross-system object-storage/"apiserver" & control-loops to automate everything; embrace desired state management & thank me latter. but, Heroku &al have a lot of value left.
there's just not that many folk trying to tame deploys on k8s via gitops. flux2 is the rage, it's all over the alpha geek's efforts[1], but it's usually used by someone carefully authoring a fairly complex Helm file, then building out a significant Flux2 HelmRelease object (ex: [2]).
there's a bunch of other tools[3], & i'm frankly not familiar enough. but this idea of having a bunch of source that can deploy itself, simply, is still extremely rare even among the alpha-geek #gitops types. i'm sure some of these tools better match the simplicity of the Heroku model, corresponding branches to environments, which makes so so much sense, but so far i feel like such attempts are still basically unknown.
heroku's really simmered it down to something that made extremely natural sense. huge props to that. too too much of this effort had to go into creating buildpacks & supporting language environments very very carefully very actively, that ability to stealth-containerize an app & not even notice is so much of the special sauce that makes this a hard, hard & eternal problem (because langauges/envs keep changing). there's still a lot of ease of use to Heroku that's potentially will be underrated and/or lost by the oncoming generations. i have high respect for how operateable Heroku is.
[1] https://github.com/k8s-at-home/awesome-home-kubernetes
[2] https://github.com/onedr0p/home-cluster/blob/main/cluster/ap...
What are some alternatives?
watchtower - A process for automating Docker container base image updates.
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
longhorn - Cloud-Native distributed storage built on and for Kubernetes
awesome-gitops - A curated list for awesome GitOps resources
RaspberryPi-Note - Raspberry Pi note
rook - Storage Orchestration for Kubernetes
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way on Google Cloud Platform. No scripts.
k8s-folding-at-home - ⛑ Run folding@home on your Kubernetes cluster
k3s - Lightweight Kubernetes
awesome-paas - A curated list of PaaS, developer platforms, Self hosted PaaS, Cloud IDEs and ADNs.
flyctl - Command line tools for fly.io services