public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-13 01:36:23 +00:00
Code Issues Releases Wiki Activity

More edits

Browse Source
This commit is contained in:
MegaShinySnivy
2023-04-18 13:34:40 -05:00
parent 89f5562c65
commit 20449e8362
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/kubernetes/persistence/nfs-subdirectory-provider.md
View File

@@ -5,7 +5,7 @@ title: Use an NFS server for your storage in Kubernetes
image: /images/<recipe name>.png
---
# {{ page.meta.recipe }} on Kubernetes
# {{ page.meta.recipe }} on Kubernetes
This storage provider allows you to use an NFS server like a native K8s storage provider, letting you to use mass storage for things like media or other large files. Why would this be useful? Things that you don't want to be replicated, for example, media (replicating 4.5TB can get expensive quick) or large data such as game servers! Of course, this does add a singe point of failure, but a lot less expensive than replicating data out to many nodes.
@@ -24,14 +24,13 @@ This storage provider allows you to use an NFS server like a native K8s storage
## Preparation
!!! warning "SQLite hates NFS"
!!! warning "SQLite hates NFS"
This recpie assumes you have an NFS server ready to go with a username and a password. Setting this up is outside the current scope of this recipe. This provider is also not to be used for persisting SQLite databases, as storing them on NFS will cause the database to corrupt.
### HelmRepository
We're going to install a helm chart from the NFS Subdirectory External Provisioner chart repository, so I create the following in my flux repo:
```yaml title="/bootstrap/helmrepositories/nfs-subdir-provider.yaml"
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
@@ -82,7 +81,6 @@ spec:
namespace: nfs-suibdir
```
### ConfigMap
Now we're into the nfs-subdir-specific YAMLs. First, we create a ConfigMap, containing the entire contents of the helm chart's [values.yaml](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/blob/master/charts/nfs-subdir-external-provisioner/values.yaml). Paste the values into a `values.yaml` key as illustrated below, indented 4 spaces (*since they're "encapsulated" within the ConfigMap YAML*). I create this example yaml in my flux repo: