CloudGraph cli VS local-path-provisioner

Looks similar to https://github.com/cloudgraphdev/cli

Honestly, half baked and not very useful at all. If you want an actual single GraphQL based API for ALL of your AWS services, plus CSPM (CIS 1.2, 1.3, 1.4, PCI, and NIST) check out https://github.com/cloudgraphdev/cli. Completely free OSS

https://github.com/cloudgraphdev/cli the GraphQL API for K8s, AWS, GCP, and Azure

Check out https://github.com/cloudgraphdev/cli. It supports a vast majority of AWS services and creates a type-safe GraphQL definition of your entire account

If you are looking for a type-safe asset inventory of your GCP footprint(s) you can check out https://github.com/cloudgraphdev/cli. Along with the asset inventory (which you can query via GraphQL) it will also check for CIS 1.2 compliance failures.

CloudGraph can give you a type-safe asset inventory (plus CIS 1.2 compliance checks) for all of your resources on GCP: https://github.com/cloudgraphdev/cli

Some great suggestions here. I would also suggest running some tool like: https://github.com/cloudgraphdev/cli with the AWS CIS policy pack so you can ensure you are following best practices.

You can use a tool like [CloudGraph](https://github.com/cloudgraphdev/cli) to do this pretty easily.

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