public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-14 10:16:27 +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

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

@@ -31,7 +31,6 @@ This storage provider allows you to use an NFS server like a native K8s storage
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: 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" ```yaml title="/bootstrap/helmrepositories/nfs-subdir-provider.yaml"
apiVersion: source.toolkit.fluxcd.io/v1beta1 apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository kind: HelmRepository
@@ -82,7 +81,6 @@ spec:
namespace: nfs-suibdir namespace: nfs-suibdir
``` ```
### ConfigMap ### 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: 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: