mizu
rook
mizu | rook | |
---|---|---|
40 | 51 | |
4,543 | 11,949 | |
- | 0.6% | |
9.7 | 9.9 | |
over 1 year ago | 2 days ago | |
C | 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.
mizu
-
The Future of Open Source, or Why Open Core Is Dead
UP9, Founded 2019, 3,743 stars
-
Interesting tools?
API traffic viewer for kubernetes(kinda like wireshark): https://github.com/up9inc/mizu
- Mizu - The API Traffic Viewer for Kubernetes
- PI traffic viewer for Kubernetes enabling you to view all API communication between microservices
- What are Kubernetes developers missing? What tool or library do you wish you had?
-
Hacker News top posts: Apr 12, 2022
Mizu – API traffic viewer for Kubernetes\ (4 comments)
- Up9inc/mizu: API traffic viewer for Kubernetes:view API comms btw microservices
-
Gain Visibility into Istio mTLS Traffic with Mizu
Mizu is an open source multi-protocol traffic viewer for Kubernetes that can be used to view API traffic between microservices communicating over synchronous and message queue protocols.Traffic viewing is essential for troubleshooting bugs, defects, and regressions. It helps developers find the root cause of a problem quicker and therefore deploy faster. Mizu is available to download as an executable binary or as source code directly from its GitHub repository.
-
How do you see TLS traffic on K8's?
As a reminder, Mizu is a lightweight API traffic viewer for Kubernetes that doesn't require any code instrumentation. It provides complete visibility to all API traffic and payloads with support for different protocols and encryption. A short video describing the new feature can be found here [Add link to video].
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?
s3-proxy - S3 Reverse Proxy with GET, PUT and DELETE methods and authentication (OpenID Connect and Basic Auth)
longhorn - Cloud-Native distributed storage built on and for Kubernetes
easyssh-proxy - easyssh-proxy provides a simple implementation of some SSH protocol features in Go
ceph-csi - CSI driver for Ceph
kubernetes - Production-Grade Container Scheduling and Management
velero - Backup and migrate Kubernetes applications and their persistent volumes
GVM - Go Version Manager
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
Ceph - Ceph is a distributed object, block, and file storage platform
Gogs - Gogs is a painless self-hosted Git service
hub-feedback - Feedback and bug reports for the Docker Hub