kubevious
rook
kubevious | rook | |
---|---|---|
16 | 51 | |
1,548 | 11,931 | |
- | 0.6% | |
6.4 | 9.9 | |
4 months ago | 7 days ago | |
TypeScript | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
kubevious
-
🎀 Five tools to make your K8s experience more enjoyable 🎀
Unlike the other tools mentioned in this post, Kubevious has no way of changing the cluster state. It is intended solely as an observability tool, focusing on potential issues in your cluster. It highlights potential threats and risks for every resource you may run.
- How do you manager what is deployed on your cluster ?
-
Interesting tools?
kubevious: UI tool and query the cluster with regex https://github.com/kubevious/kubevious
- What do you think of this proposal? "Feature Proposal: Kubevious Guard - best practices enforcer"
-
Looking for contributors for a K8s related open-source project
Project: Kubevious
- We are starting Week Community Meetings for Kubevious users and contributors. Join to learn current state of Kubevious, discuss future development items and or just meet smart folks. Every Thursday @ 9am PST on Zoom. Details in the GitHub link.
- Started Kubevious Weekly Community Meeting to build a community around the project. If you're in Kubernetes space and are available to help, please join the meeting to chat. Instructions to join are in the README. See you there!
-
Kubernetes Dashboard: 10 Alternatives You Should Consider
In many ways, Kubevious is like many other Kubernetes Dashboard alternatives in that it provides the capability to view, edit, and maintain your configurations. However, Kubevious is going strong on one specific selling point: simplicity.
-
Help: Need feedback on K8s UI redesign
But since you asked I’ll give quick summary to the scope of the change. Prior version of Kubevious comes with a graphival view, where resources are reresented in a tree structure under namespaces and grouped in a logical group of “application”. This lets you see configmaps, services, ingresses, etc that are somehow related to this application. See here: https://github.com/kubevious/kubevious
- How to validate Kubernetes YAML files
rook
-
Ceph: A Journey to 1 TiB/s
I have some experience with Ceph, both for work, and with homelab-y stuff.
First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes.
For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines.
Also, Ceph does prefer physical access to disks (similar to ZFS).
And you do need decent networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).
But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.
You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).
Hope this helps, and good luck! Let me know if you have any other questions.
-
Running stateful workloads on Kubernetes with Rook Ceph
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case of a disaster.
-
People who run Nextcloud in Docker: Where do you store your data/files? In a Docker volume, or on a remote server/NAS?
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself.
-
Rook/Ceph with VM nodes on research cluster?
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:
-
Asking for recommendation on remote Kubernetes storage for a small cluster and databases
Have you looked at Rook?
-
Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.
-
ATARI is still alive: Atari Partition of Fear
This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
Rook (this is a nice article for Rook NFS)
-
Running on-premise k8s with a small team: possible or potential nightmare?
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc
-
My completely automated Homelab featuring Kubernetes
I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.
What are some alternatives?
lens - Lens - The way the world runs Kubernetes
longhorn - Cloud-Native distributed storage built on and for Kubernetes
komoplane - 🍨 Crossplane Troubleshooting Tool by Komodor
ceph-csi - CSI driver for Ceph
kube-linter - KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.
velero - Backup and migrate Kubernetes applications and their persistent volumes
openunison-k8s-login-oidc - Kubernetes login portal for both kubectl and the dashboard using OpenID Connect. Use groups from your assertion in RBAC policies to control access to your cluster. Supports impersonation and OpenID Connect integration with your API server.
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
k8dash - Simple Kubernetes real-time dashboard and management.
Ceph - Ceph is a distributed object, block, and file storage platform
Flux - Successor: https://github.com/fluxcd/flux2
hub-feedback - Feedback and bug reports for the Docker Hub