From 16ef06ffb363b6304d0d5269b30dedbdd07288df Mon Sep 17 00:00:00 2001 From: "Gabriel A. Giovanini" Date: Sat, 14 May 2022 00:00:22 +0200 Subject: feat: Add title parser Add title parse so it yields a better post list. --- content/posts/2021-12-26-nfs-k3s.html | 60 ---------------------- content/posts/Enable_NFS_on_K3S.html | 60 ++++++++++++++++++++++ .../K8S_private_gitlab_registry_using_podman.html | 1 - 3 files changed, 60 insertions(+), 61 deletions(-) delete mode 100644 content/posts/2021-12-26-nfs-k3s.html create mode 100644 content/posts/Enable_NFS_on_K3S.html (limited to 'content') diff --git a/content/posts/2021-12-26-nfs-k3s.html b/content/posts/2021-12-26-nfs-k3s.html deleted file mode 100644 index 09f91e7..0000000 --- a/content/posts/2021-12-26-nfs-k3s.html +++ /dev/null @@ -1,60 +0,0 @@ -
-

- By default K3S comes only with local-path storage class, and if you are - running - with more than one node in your cluster you may want to use a more “distributed” - solution. For may case I opted for NFS. -

-

- To check the current storage class you can run: -

- 
k3s kubectl get storageclasses
-

- And it will print something like: -

- 
NAME                   PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
-local-path (default)   rancher.io/local-path                           Delete          WaitForFirstConsumer   false                  154d
-

- To start adding First you need to install helm on your server. To do - so you may - run: -

- - 
curl -sSL https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
-

- Be careful when running scripts directly into bash always check the source - Sometimes is also recommended to do not pipe directly to bash -

-

- Once it is installed we need to add the NFS storage classes. It has two - providers, I have chose NFS Subdir - External Provisioner. -

-

- Add the helm repo -

- - 
helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
-

- Then we need to actually install the provider -

-
-
helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner
---set nfs.server=x.x.x.x
---set nfs.path=/exported/path
-
-

- Set the nfs.server and nfs.path accordingly with your setup. -

- -

- After that if we run k3s kubectl get storageclasses it will now print another - NFS provider: -

- - 
NAME                   PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
-local-path (default)   rancher.io/local-path                           Delete          WaitForFirstConsumer   false                  154d
-nfs-client             cluster.local/nfs-subdir-external-provisioner   Delete          Immediate              true                   76m
-
diff --git a/content/posts/Enable_NFS_on_K3S.html b/content/posts/Enable_NFS_on_K3S.html new file mode 100644 index 0000000..09f91e7 --- /dev/null +++ b/content/posts/Enable_NFS_on_K3S.html @@ -0,0 +1,60 @@ +
+

+ By default K3S comes only with local-path storage class, and if you are + running + with more than one node in your cluster you may want to use a more “distributed” + solution. For may case I opted for NFS. +

+

+ To check the current storage class you can run: +

+ 
k3s kubectl get storageclasses
+

+ And it will print something like: +

+ 
NAME                   PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+local-path (default)   rancher.io/local-path                           Delete          WaitForFirstConsumer   false                  154d
+

+ To start adding First you need to install helm on your server. To do + so you may + run: +

+ + 
curl -sSL https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
+

+ Be careful when running scripts directly into bash always check the source + Sometimes is also recommended to do not pipe directly to bash +

+

+ Once it is installed we need to add the NFS storage classes. It has two + providers, I have chose NFS Subdir + External Provisioner. +

+

+ Add the helm repo +

+ + 
helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
+

+ Then we need to actually install the provider +

+
+
helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner
+--set nfs.server=x.x.x.x
+--set nfs.path=/exported/path
+
+

+ Set the nfs.server and nfs.path accordingly with your setup. +

+ +

+ After that if we run k3s kubectl get storageclasses it will now print another + NFS provider: +

+ + 
NAME                   PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+local-path (default)   rancher.io/local-path                           Delete          WaitForFirstConsumer   false                  154d
+nfs-client             cluster.local/nfs-subdir-external-provisioner   Delete          Immediate              true                   76m
+
diff --git a/content/posts/K8S_private_gitlab_registry_using_podman.html b/content/posts/K8S_private_gitlab_registry_using_podman.html index 06306ed..43b8245 100644 --- a/content/posts/K8S_private_gitlab_registry_using_podman.html +++ b/content/posts/K8S_private_gitlab_registry_using_podman.html @@ -36,5 +36,4 @@ kubectl create secret generic regcred \ NAME TYPE DATA AGE regcred kubernetes.io/dockerconfigjson 1 53s

- -- cgit v1.2.3