Shell k3s

Open-source Shell projects categorized as k3s

Top 17 Shell k3 Projects

  • home-ops

    Wife approved HomeOps driven by Kubernetes and GitOps using Flux

    Project mention: Rebuilding my homelab: Suffering as a service | news.ycombinator.com | 2024-05-18

    This is incredibly popular a take, and this anti-k8s is rapidly upvoted almost every time.

    The systemd hate has cooled a bit, but it too functions as a sizable attractor for disdain & accusation hurling. Let's look at one of my favorite excerpts from the article, on systemd:

    > Fleet was glorious. It was what made me decide to actually learn how to use systemd in earnest. Before I had just been a "bloat bad so systemd bad" pleb, but once I really dug into the inner workings I ended up really liking it. Everything being composable units that let you build up to what you want instead of having to be an expert in all the ways shell script messes with you is just such a better place to operate from. Not to mention being able to restart multiple units with the same command, define ulimits, and easily create "oneshot" jobs. If you're a "systemd hater", please actually give it a chance before you decry it as "complicated bad lol". Shit's complicated because life is complicated.

    Shits complicated because life is complicated. In both cases, having encompassing ways to compose connectivity has created a stable base - starting point to expert/advanced capable - that allowed huge communities to bloom. Rather than every person being out there by ourselves, the same tools work well for all users, the same tools are practiced with the same conventions.

    Overarching is key to commanlity being possible. You could walk up to my computer and run 'systemd cat' on any service on it, and quickly see how stuff was setup (especially on my computers which make heavy use of environment variables where possible); before every distro and to a sizable degree every single program was launched & configured differently, requires plucking through init scripts to see how or if the init script was modified. But everything has a well defined shape and form in systemd, a huge variety of capabilities for controlling launch characteristics, process isolation, ulimits, user/group privileges, special tmp directories is all provided out of the box in a way that means there's one man page to go to, and that's instantly visible, so we don't have to go spelunking.

    The Cloud Native paradigm that Kubernetes practices is a similar work of revelation, offering similar batteries included capabilities. Is it confusing having pods, replicasets, and services? Yes perhaps at first. But it's unparalleled that one just POSTs resources one wants to an API-server and let's the system start & keep that running; this autonomic behavior is incredibly freeing, leaving control loops doing what humans have had to shepherd & maintain themselves for decades; a paradigm break turning human intent directly into consistent running managed systems.

    The many abstractions/resource types are warranted, they are separate composable pieces that allow so much. Need to serve on a second port? Easy. Why are there so many different types? Because computers are complex, because this is a model of what really is. Maybe we can reshuffle to get different views, but most of that complexity will need to stay around, but perhaps in refactores shapes.

    And like systemd, Kubernetes with it's Desired State Management and operators, it creates a highly visible highly explorable system; any practitioner can walk up to any cluster and start gleening tons of information from it, can easily see it run.

    It's a wrong hearted view to think that simpler is better. We should start with essential complexity & figure out simultaneously a) how to leverage and b) how to cut direct paths through our complex capable systems. We gain more by permitting and enabling than by pruning. We gain my by being capable of working at both big and small scales than we gain by winnowing down/down scoping our use cases. The proof is in the pudding. Today there's hundreds of guides one can go through in an hour to setup & get started running some services on k3s. Today there's a colossal communities of homelab operators sharing helm charts & resources (ex: https://github.com/onedr0p/home-ops), the likes of which has vastly outclassed where we have stood before. Being afraid of & shying away from complexity is a natural response, but i want people to show that they see so many of the underlying simplicities & conceptions that we have gotten from kube that do make things vastly simpler than the wild West untamed world we came from, where there weren't unified patterns of API servers & operators, handling different resources but all alike & consistent. To conquer complexity you must understand it, and I think very few of those with a true view of Kubernetes complexity have the sense that there are massive opportunities for better, for simpler. To me, the mission, the goal, the plan should be to better manage & better package Kubernetes to better onboard & help humans through it, to try to walk people into what these abstractions are for & shine lights on how they all mirror real things computers need to be doing.

    (Technical note, Kubernetes typically runs 0 vm's, it runs containers. With notable exceptions being snap-in OCI runtimes like Firecracker and Kata which indeed host pods as vms. Kine relies on containers are far more optimizable; works like Puzzlefs and Composefs CSIs can snap-in to allow vastly more memory-and-storage-efficient filesystems to boot. So many wonderful pluggable/snappable layers; CNI for networking too.)

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • smallab-k8s-pve-guide

    A guide series explaining how to setup a personal small homelab running a Kubernetes cluster with VMs on a Proxmox VE standalone server node.

  • k8s-gitops

    GitOps principles to define kubernetes cluster state via code

  • freeipa-container

    FreeIPA server in containers — images at https://quay.io/repository/freeipa/freeipa-server?tab=tags

  • pi-cluster

    Pi Kubernetes Cluster. Homelab kubernetes cluster automated with Ansible and ArgoCD

  • k3d-demo

    Demo of k3d: Tool to run k3s (Kubernetes) in Docker

  • k3d-action

    A GitHub Action to run lightweight ephemeral Kubernetes clusters during workflow. Fundamental advantage of this action is a full customization of embedded k3s clusters. In addition, it provides a private image registry and multi-cluster support.

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
  • vagrant-k3s-HA-cluster

    This repository contains the Vagrantfile and scripts to easily configure a Highly Available Kubernetes (K3s) cluster.

  • k3s-rpi-cluster

    Setting up a K3S Kubernetes cluster using RPI4

  • k3s-multipass-bootstrap

    Bootstrap script to get a k3s Cluster created with Multipass for local development.

  • local-kubernetes-runner

    CLI for spins up a K8s cluster locally in 10 seconds.

    Project mention: Show HN: Dev Kubernetes cluster in 10 seconds – Docker is the only requirement | news.ycombinator.com | 2024-06-04
  • scooby

    Pretty fast, pretty simple K3S clusters for Raspberry Pi (by rayui)

    Project mention: Scooby – Pretty fast, pretty simple K3S clusters for Raspberry Pi | news.ycombinator.com | 2023-08-17
  • kube-config

    Luke's kubeconfig

    Project mention: Home Assistant 2023.11 | news.ycombinator.com | 2023-11-02

    Helm is an absolute mess in my experience.

    I'm using zigbee2mqtt in K8s and just pinning the deployment to a node and mapping the device as a volume: https://github.com/LukeChannings/kube-config/blob/3b61c7607c...

    Should work the same for Home Assistant, but I don't use HA for Zigbee directly, instead using z2m -> MQTT -> HA, which I've found to be very robust.

    I'm waiting for a new K8s cluster (based on CM4) and when I re-implement all of this I'll get a network-based PoE Zigbee device (https://smlight.tech/manual/slzb-06/), that way I can un-pin the deployment and look at high availability Zigbee via MQTT (something Home Assistant doesn't support)

  • ansible-libvirt-microos

    An ansible role for spinning up a VM using microos

    Project mention: OpenSUSE Leap 15.6 to Be the Last in Its Current Form | news.ycombinator.com | 2024-01-16
  • kube-ghost

  • gitops

    A re-usable mono repository for my Kubernetes clusters which adheres to Infrastructure as Code (IaC) and GitOps practices where possible - with re-usable workload definitions across clusters.

  • podman-appimage

    Podman AppImage: A portable tool for managing OCI containers and pods.

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020).

Shell k3s discussion

Log in or Post with

Shell k3s related posts

  • Rebuilding my homelab: Suffering as a service

    5 projects | news.ycombinator.com | 18 May 2024
  • OpenSUSE Leap 15.6 to Be the Last in Its Current Form

    1 project | news.ycombinator.com | 16 Jan 2024
  • Opensuse microos and environment

    1 project | /r/openSUSE | 3 Jul 2023
  • Project to make a custom linux desktop experience that benefits from group knowledge and experience (Part 1)

    2 projects | /r/ScientificComputing | 25 Jun 2023
  • Immutable openSUSE ?

    1 project | /r/openSUSE | 8 Jun 2023
  • Is OpenSuse Leap safe to install now ?

    1 project | /r/openSUSE | 30 May 2023
  • most updated distro

    1 project | /r/linux_gaming | 24 Apr 2023
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 17 Jul 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Index

What are some of the best open-source k3 projects in Shell? This list will help you:

Project Stars
1 home-ops 1,846
2 smallab-k8s-pve-guide 748
3 k8s-gitops 627
4 freeipa-container 586
5 pi-cluster 352
6 k3d-demo 255
7 k3d-action 174
8 vagrant-k3s-HA-cluster 44
9 k3s-rpi-cluster 30
10 k3s-multipass-bootstrap 17
11 local-kubernetes-runner 16
12 scooby 14
13 kube-config 13
14 ansible-libvirt-microos 5
15 kube-ghost 3
16 gitops 1
17 podman-appimage 0

Sponsored
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com