external-snapshotter VS home-ops

By the way, I got that error very often - kubernetes-csi/external-snapshotter#300 - the fix is in progress. I'm afraid about the snapshot mechanism performance. It's also a question about the GCP snapshot mechanism, so I'm gathering opinions.

VolSync is a much better option than Velero IMO, Velero was created before GitOps was a thing and it really tries to do too much when all I need is a reliable way to backup and restore PVCs. If your CSI supports volume snapshots, VolSync can use the snapshot-controller to create Volume Snapshots and then mount those as a PVC to a temporary pod to then backup that up to S3. This is really great for backing up PVCs because it's not backing them up from a running workload.

Is it required to store it to s3? If I were U i would use native approach https://kubernetes.io/docs/concepts/storage/volume-snapshots/ with https://github.com/kubernetes-csi/external-snapshotter

#Install CSI Snapshotter and CRDs kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotcontents.yaml kubectl apply -n kube-system -f https://github.com/kubernetes-csi/external-snapshotter/raw/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshotclasses.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/client/config/crd/snapshot.storage.k8s.io_volumesnapshots.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml kubectl apply -n kube-system -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/master/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml

These are great operational wins. Agreed very much that having autonomic (can fix itself) systems at your back is a massive game changer. De-crustifies the act of running things.

The other win is that there's a substantial cultural base to this way to go. Folks have been doing selfhosting for ages, but everyone has their own boutique setup some their way. A couple tools and techniques could be shared, but mostly everyone took blank slate configs & built their own system up, & added their own monitoring & operational scripts.

https://github.com/onedr0p/home-ops is a set of helm scripts and other tools that is widely widely used, and there's a lot more like it. It's a huge build out, using convention and a common platform to enable portable knowledge & sharing.

Self hosting did not have intellectual scale out at it's back, before Kubernetes came along. Docker and ansible and others have been around, but theres never been remotely the success there has been today in empowering users to setup & run complex services.

We really have clawed out of the server-hugging jungle &started building some villages. It's wonderful to see.

Going thru this repo https://github.com/onedr0p/home-ops

Take a look at my open source GitOps repo managed by Flux here: https://github.com/onedr0p/home-ops

Im fully onboard with the geneneral idea as a target.

Right now it's for early early adopters. Hosting stuff is still a painm But we are getting better at hosting stuff, finding stable patterns, paving the path. Hint, it's not doing less, it's not simpler options: it's adopting & making our own industrial scale tooling. https://github.com/onedr0p/home-ops is a great early & still strong demonstration; the up front cost od learning is high, but there's the biggest ecosystem of support you can imagine, and once you recognize the patterns, you can get into flow states, make stuff happen, with extreme leverage far beyond where humanity has ever been. Building the empowered individual is happening, and we're using stable good patterns that will mean the individual isnt so off on their own doing ops- they'll have a lot more accrued human experiene at their back, their running of services isnt as simple to understand from the start but goes much much further, is much more mature & well supported in the long run.

My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.

For example: https://github.com/onedr0p/home-ops/pull/4528

I'm running minio in my cluster with NFS backend just fine. You can see my deployment of it here.