nfs-subdir-external-provisioner
helm
Our great sponsors
nfs-subdir-external-provisioner | helm | |
---|---|---|
48 | 206 | |
2,364 | 26,013 | |
4.3% | 1.1% | |
4.2 | 9.0 | |
20 days ago | 3 days ago | |
Shell | 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.
nfs-subdir-external-provisioner
-
Investigating a failed VolumeSnapshot with NFS on Kubernetes
Using nfs-subdir-external-provisioner instead of csi-driver-nfs
-
Database corruption
I am trying to run sonarr inside my k3s cluster. Since I have multiple nodes, in order to keep data persistant I have been using a NAS and the Kubernetes NFS external provisioner as my Storage Class.
-
Utilizing traditional storage in a modern way
There's this, if you want your nfs storage available to pods as PVCs, with some limitations: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner
-
Help me What to Choose?
NFS Provisioner
- [GUIDE] How to deploy the Servarr stack on Kubernetes with Terraform!
-
Longhorn alternatives
Depends on how much resiliency you need . Something like https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner works well for a lab or non-prod cluster. You could even use something like this in prod if you have access to highly reliably NFS mounts.
-
Recommendations for k8s storage solution
I first installed a NFS Server via this helm chart: https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner Eventually I deployed Longhorn cause I needed expandable volumes, which the first repo doesn't support. I guess for best performance you should go for a ceph cluster, but I'm not an expert.
-
Move to K8s for hosting at home?
I used the NFS provisioner for persistent volumes until I got the Ceph side up and running. I created a share on my NAS specifically for k8s. It worked very well and had the bonus of being just a regular file system that you could browse/edit easily (just place files in or edit config). I would agree with not moving plex into k8s. I right now just have a barebones 1 control 2 worker setup using k3s.
-
K8s - Self hosted PaaS?
However, is it too difficult to create new pods/deployments etc on your own? I find it super easy to just create a PVC (via https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner ) and create a MySQL pod in a new namespace for every micro service I create.
-
Unsure how NFS Persistent Volumes work, please help!
This is what you need https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner Point it to a folder and it will create subfolders for each PVC.
helm
-
Kubernetes CI/CD Pipelines
Applying Kubernetes manifests individually is problematic because files can get overlooked. Packaging your applications as Helm charts lets you version your manifests and easily repeat deployments into different environments. Helm tracks the state of each deployment as a "release" in your cluster.
-
deploying a minio service to kubernetes
helm
-
How to take down production with a single Helm command
Explanation here: https://github.com/helm/helm/issues/12681#issuecomment-19593...
Looks like it's a bug in Helm, but actually isn't Helm's fault, the issue was introduced by Fedora Linux.
-
Building a VoIP Network with Routr on DigitalOcean Kubernetes: Part I
Helm (Get from here https://helm.sh/)
-
The 2024 Web Hosting Report
It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity.
-
Deploying a Web Service on a Cloud VPS Using Kubernetes MicroK8s: A Comprehensive Guide
Kubernetes orchestrates deployments and manages resources through yaml configuration files. While Kubernetes supports a wide array of resources and configurations, our aim in this tutorial is to maintain simplicity. For the sake of clarity and ease of understanding, we will use yaml configurations with hardcoded values. This method simplifies the learning process but isn’t ideal for production environments due to the need for manual updates with each new deployment. Although there are methods to streamline and automate this process, such as using Helm charts or bash scripts, we’ll not delve into those techniques to keep the tutorial manageable and avoid fatigue — you might be quite tired by that point!
-
Deploy Kubernetes in Minutes: Effortless Infrastructure Creation and Application Deployment with Cluster.dev and Helm Charts
Helm is a package manager that automates Kubernetes applications' creation, packaging, configuration, and deployment by combining your configuration files into a single reusable package. This eliminates the requirement to create the mentioned Kubernetes resources by ourselves since they have been implemented within the Helm chart. All we need to do is configure it as needed to match our requirements. From the public Helm chart repository, we can get the charts for common software packages like Consul, Jenkins SonarQube, etc. We can also create our own Helm charts for our custom applications so that we don’t need to repeat ourselves and simplify deployments.
-
Kubernets Helm Chart
We can search for charts https://helm.sh/ . Charts can be pulled(downloaded) and optionally unpacked(untar).
-
Introduction to Helm: Comparison to its less-scary cousin APT
Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM.
-
🎀 Five tools to make your K8s experience more enjoyable 🎀
Within the architecture of Cyclops, a central component is the Helm engine. Helm is very popular within the Kubernetes community; chances are you have already run into it. The popularity of Helm plays to Cyclops's strength because of its straightforward integration.
What are some alternatives?
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
crossplane - The Cloud Native Control Plane
longhorn - Cloud-Native distributed storage built on and for Kubernetes
kubespray - Deploy a Production Ready Kubernetes Cluster
nfs-ganesha-server-and-external-provisioner - NFS Ganesha Server and Volume Provisioner.
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
csi-s3 - A Container Storage Interface for S3
krew - 📦 Find and install kubectl plugins
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
skaffold - Easy and Repeatable Kubernetes Development
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
dapr-demo - Distributed application runtime demo with ASP.NET Core, Apache Kafka and Redis on Kubernetes cluster.