-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathnfslabbreakdown.txt
More file actions
36 lines (28 loc) · 1.66 KB
/
nfslabbreakdown.txt
File metadata and controls
36 lines (28 loc) · 1.66 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
WHAT JUST HAPPENED?? 💻 Persistent Storage with NFS
Part 1:
- get an NFS server deployment running inside our cluster
- put a server pod on every node so the server can be accessed from anywhere in the cluster
- ...but it's not ready to be used yet!
Part 2:
- create a storageClass that allows persistent volumes to use the NFS server.
Part 3:
- make a PV, PVC, and Pod- then make a test file inside the Pod. Then test that the file is accessible from any node in the cluster!
--------------
Steps 1-13:
Install the NFS server. Break down what got installed.
• the NFS server itself, which is in a deployment
• a ServiceAccount to manage the NFS server as well as all the permissions it needs to do so (RBAC)
• a deployment that the ServiceAccount uses to manage the NFS server
• the CSI driver for NFS storage, enabling this storage to work
• A DaemonSet that puts a pod on every node, enabling the NFS server to be accessed from every node.
Step 16:
• Install Jinja2, a templating engine that allows you to "fill in the blanks" on template files. Handy for populating files from the command line.
Steps 17-20:
• Insert the IP address that leads to your NFS server into a StorageClass manifest.
• Create the StorageClass for the NFS storage we've set up. Allows our cluster to now use this type of storage.
Steps 21-26:
• Create a PersistentVolume, a PersistentVolumeClaim, and a Pod that mounts that PVC.
Steps 27-END:
• Confirm that the PVC mountPath in the Pod is connected to our NFS server.
• Create a file in that mountPath.
• Send a "cat file" command to one of the NFS server Pods to confirm the file is saved at that location and our storage solution works!