mizu VS local-path-provisioner

UP9, Founded 2019, 3,743 stars

API traffic viewer for kubernetes(kinda like wireshark): https://github.com/up9inc/mizu

Mizu – API traffic viewer for Kubernetes\ (4 comments)

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.

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].

Deploy local-path-provisioner storage class but it does not support readwritemany so for high availability of your Kubernetes cluster better to use longhorn

I use this one. I'm waiting for the day it's combined with syncthing to sync across all nodes. https://github.com/rancher/local-path-provisioner

So I have this single node k3s cluster. k3s uses local-path (https://github.com/rancher/local-path-provisioner) as default SC that allows one to create dynamic volumes using nodes local storage.

Just create 1 single partition and format it with whatevery filesystem you like. And then use ranchers local-path-provisioner which will create a folder per PV (k3s has this integrated by default).

Tinkering locally with local path provisioner (https://github.com/rancher/local-path-provisioner), I find that I can delete and re-create the pod, and the data persists on disk. However, if I delete the PVC, when I recreate the PVC, a new directory on disk is created.

It is better to use https://github.com/rancher/local-path-provisioner (or similar) for this case which will do PVC on local directories because manually linking PV<>PVC will not work.

Since you only have one physical node anyway, I would just make the cluster a single-node cluster (1 VM) and use local storage on that VM. I’m biased though because this is what I do (I run K3s and use local path provisioner).

Rancher's Local Path Provisioner - From reading, seems to just use HostPath or Local PVs under the hood, but adds dynamic provisoning

With any of those tools, you'd implement a network storage on top of a network storage. I would go with mouting few volumes per node +local storage like (https://github.com/rancher/local-path-provisioner).