From 20449e8362750a066fb7ee0d7f09c96664124b53 Mon Sep 17 00:00:00 2001 From: MegaShinySnivy Date: Tue, 18 Apr 2023 13:34:40 -0500 Subject: [PATCH] More edits --- docs/kubernetes/persistence/nfs-subdirectory-provider.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/kubernetes/persistence/nfs-subdirectory-provider.md b/docs/kubernetes/persistence/nfs-subdirectory-provider.md index 948b05a..d501324 100644 --- a/docs/kubernetes/persistence/nfs-subdirectory-provider.md +++ b/docs/kubernetes/persistence/nfs-subdirectory-provider.md @@ -5,7 +5,7 @@ title: Use an NFS server for your storage in Kubernetes image: /images/.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: