cstor-operators
home-ops
Our great sponsors
cstor-operators | home-ops | |
---|---|---|
4 | 52 | |
93 | 1,723 | |
- | - | |
5.1 | 10.0 | |
4 months ago | about 19 hours ago | |
Go | Shell | |
Apache License 2.0 | Do What The F*ck You Want To Public License |
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.
cstor-operators
-
Why OpenEBS 3.0 for Kubernetes and Storage?
OpenEBS CStor (declared stable), has added support for a CSI Driver and also improved customer resources and operators for managing the lifecycle of CStor Pools. This 3.0 version of the CStor includes:
-
32 Node KBN-I/5200 Kubernetes cluster running Debian 10/K8s 1.17/Intel Core i7/8GB RAM each. Used the standoffs and mounted each 8 stack to empty trays. Disks are 64GB USB3 sticks.
It's a little complicated at first but there's also OpenEBS and Longhorn. Longhorn is probably the most easiest to get going with, but I chose rook-ceph because it's very stable.
-
Looking for a sanity check on a project I'm working on at home, hoping you fine people can help - Raspberry Pi Kubernetes Cluster
- SMB CSI: https://github.com/kubernetes-csi/csi-driver-smb - OpenEBS if you got the hardware for it: https://openebs.io/
-
Best Open-Source Distributed Parallel Storage Option for an AI/ML Cluster?
Tried OpenEBS? These two have replication HA features. https://github.com/openebs/Mayastor https://github.com/openebs/cstor-operators
home-ops
-
Ditching PaaS: Why I Went Back to Self-Hosting
These are great operational wins. Agreed very much that having autonomic (can fix itself) systems at your back is a massive game changer. De-crustifies the act of running things.
The other win is that there's a substantial cultural base to this way to go. Folks have been doing selfhosting for ages, but everyone has their own boutique setup some their way. A couple tools and techniques could be shared, but mostly everyone took blank slate configs & built their own system up, & added their own monitoring & operational scripts.
https://github.com/onedr0p/home-ops is a set of helm scripts and other tools that is widely widely used, and there's a lot more like it. It's a huge build out, using convention and a common platform to enable portable knowledge & sharing.
Self hosting did not have intellectual scale out at it's back, before Kubernetes came along. Docker and ansible and others have been around, but theres never been remotely the success there has been today in empowering users to setup & run complex services.
We really have clawed out of the server-hugging jungle &started building some villages. It's wonderful to see.
-
Homelab setup for Kubernetes training
Going thru this repo https://github.com/onedr0p/home-ops
- Selfhosted k8s for home server?
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
Take a look at my open source GitOps repo managed by Flux here: https://github.com/onedr0p/home-ops
- How do You manage Your docker containers configuration?
-
Self Hosted SaaS Alternatives
Im fully onboard with the geneneral idea as a target.
Right now it's for early early adopters. Hosting stuff is still a painm But we are getting better at hosting stuff, finding stable patterns, paving the path. Hint, it's not doing less, it's not simpler options: it's adopting & making our own industrial scale tooling. https://github.com/onedr0p/home-ops is a great early & still strong demonstration; the up front cost od learning is high, but there's the biggest ecosystem of support you can imagine, and once you recognize the patterns, you can get into flow states, make stuff happen, with extreme leverage far beyond where humanity has ever been. Building the empowered individual is happening, and we're using stable good patterns that will mean the individual isnt so off on their own doing ops- they'll have a lot more accrued human experiene at their back, their running of services isnt as simple to understand from the start but goes much much further, is much more mature & well supported in the long run.
- Deploying apache guacamole on k8s
-
My completely automated Homelab featuring Kubernetes
My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.
-
Container Updating Strategies
For example: https://github.com/onedr0p/home-ops/pull/4528
-
Simple self-hosted S3-compatible
I'm running minio in my cluster with NFS backend just fine. You can see my deployment of it here.
What are some alternatives?
Mayastor - Dynamically provision Stateful Persistent Replicated Cluster-wide Fabric Volumes & Filesystems for Kubernetes that is provisioned from an optimized NVME SPDK backend data storage stack.
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
jiva-operator - Kubernetes Operator for managing Jiva Volumes via custom resource.
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
openebs - Most popular & widely deployed Open Source Container Native Storage platform for Stateful Persistent Applications on Kubernetes.
longhorn - Cloud-Native distributed storage built on and for Kubernetes
gocast - GoCast is a tool for controlled BGP route announcements from a host
zfs-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend ZFS data storage stack.
motioneye - A web frontend for the motion daemon.
dynamic-nfs-provisioner - Operator for dynamically provisioning an NFS server on any Kubernetes Persistent Volume. Also creates an NFS volume on the dynamically provisioned server for enabling Kubernetes RWX volumes.
renovate-helm-releases - Creates Renovate annotations in Flux2 Helm Releases