local-path-provisioner VS kubespy

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

lang="en"> charset="utf-8"> Hello, world! Hello, world! 👋 Deployed with 💜 by new href="https://pulumi.com/">Pulumi.

Pulumi IaC will help us bring up our infrastructure on the AWS Cloud. Check out pulumi.com if you still need to become familiar with it. You can deploy this demo stack using the Pulumi button below.

There are other infrastructure as code tools that take secrets seriously. Pulumi encrypts all values in state and you can even bring your own key from your cloud provider

*Codifying the deployment of the OTel Collector *(to Nomad, Kubernetes, or a VM) using tools such as Terraform, Pulumi, or Ansible. The Collector funnels your OTel data to your Observability back-end. ✅

KubeSpy - to see what's going on a deployment real time. https://github.com/pulumi/kubespy

it takes too much time, terraform configs are not easy to use also. Pulumi is much better to maintenance. Cloudy is good enough for launching a production-ready cluster in 5-10 minutes. It could be an alternative to kops

Just wanted to mention a Terraform alternative I really like, especially cause it's infrastructure as code (IaC) http://pulumi.com/, though I'm not sure about their approach on multi cloud, haven't used it in quite a while

That is the entire point of Pulumi, you should give it a try

pulumi.com if you are interested in doing anything dynamic inside of your templates (i.e. conditions) take a look at pulumi