feat: Move code to blog

- Move most logic of the blog to blog.rs, making it easier to test.
- Now the file contains the creation date of the blog post to be parsed.
- Add chrono to parse datetime, so later we can order by date.
- Refactor gitlab pipeline, move `before_script` to a proper place.

1 files changed, 60 insertions, 0 deletions

diff --git a/content/posts/2021-12-26Enable_NFS_on_K3S.html b/content/posts/2021-12-26Enable_NFS_on_K3S.html
new file mode 100644
index 0000000..09f91e7
--- /dev/null
+++ b/content/posts/2021-12-26Enable_NFS_on_K3S.html
@@ -0,0 +1,60 @@
+<section>
+    <p>
+        By default <a href="https://k3s.io/">K3S</a> comes only with <a
+            href="https://github.com/rancher/local-path-provisioner">local-path</a> storage class, and if you are
+        running
+        with more than one node in your cluster you may want to use a more &ldquo;distributed&rdquo;
+        solution. For may case I opted for NFS.
+    </p>
+    <p>
+        To check the current storage class you can run:
+    </p>
+    <pre><code>k3s kubectl get storageclasses</code></pre>
+    <p>
+        And it will print something like:
+    </p>
+    <pre><code>NAME                   PROVISIONER                                     RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+local-path (default)   rancher.io/local-path                           Delete          WaitForFirstConsumer   false                  154d</code></pre>
+    <p>
+        To start adding First you need to install <a href="https://github.com/helm/helm">helm</a> on your server. To do
+        so you may
+        run:
+    </p>
+
+    <pre><code>curl -sSL https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash</code></pre>
+    <p>
+        Be careful when running scripts directly into bash always check the source
+        Sometimes is also recommended to do not pipe directly to bash
+    </p>
+    <p>
+        Once it is installed we need to add the <a
+            href="https://kubernetes.io/docs/concepts/storage/storage-classes/#nfs">NFS storage classes</a>. It has two
+        providers, I have chose <a href="https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner">NFS Subdir
+        External Provisioner</a>.
+    </p>
+    <p>
+        Add the helm repo
+    </p>
+
+    <pre><code>helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/</code></pre>
+    <p>
+        Then we need to actually install the provider
+    </p>
+    <div class="org-src-container">
+<pre><code>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</code></pre>
+    </div>
+    <p>
+        Set the <code>nfs.server</code> and <code>nfs.path</code> accordingly with your setup.
+    </p>
+
+    <p>
+        After that if we run <code>k3s kubectl get storageclasses</code> it will now print another
+        NFS provider:
+    </p>
+
+    <pre><code>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</code></pre>
+</section>