From e964ec8f74b644d66ca166a7524adcc3a82709c9 Mon Sep 17 00:00:00 2001 From: "Gabriel A. Giovanini" Date: Sat, 14 May 2022 19:56:06 +0200 Subject: 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. --- .../posts/2020-07-14Friz_box_turned_off_DHCP.html | 18 +++++++ content/posts/2021-12-26Enable_NFS_on_K3S.html | 60 ++++++++++++++++++++++ ...26K8S_private_gitlab_registry_using_podman.html | 39 ++++++++++++++ content/posts/Enable_NFS_on_K3S.html | 60 ---------------------- content/posts/Friz.box_turned_off_DHCP.html | 18 ------- .../K8S_private_gitlab_registry_using_podman.html | 39 -------------- 6 files changed, 117 insertions(+), 117 deletions(-) create mode 100644 content/posts/2020-07-14Friz_box_turned_off_DHCP.html create mode 100644 content/posts/2021-12-26Enable_NFS_on_K3S.html create mode 100644 content/posts/2021-12-26K8S_private_gitlab_registry_using_podman.html delete mode 100644 content/posts/Enable_NFS_on_K3S.html delete mode 100644 content/posts/Friz.box_turned_off_DHCP.html delete mode 100644 content/posts/K8S_private_gitlab_registry_using_podman.html (limited to 'content') diff --git a/content/posts/2020-07-14Friz_box_turned_off_DHCP.html b/content/posts/2020-07-14Friz_box_turned_off_DHCP.html new file mode 100644 index 0000000..569604b --- /dev/null +++ b/content/posts/2020-07-14Friz_box_turned_off_DHCP.html @@ -0,0 +1,18 @@ +
+

Friz.box turned off DHCP

+

+ If you turned off your DHCP server follow these steps to connect to FritzBox settings. +
+

+

+

+ On gnome turn the wired connection off on again to apply the settings. +

+

+ Note: why in the hell does FritzBox 7490 require a land-line telephone to be physically factory + reset? +

+
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 @@ +
+

+ 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/2021-12-26K8S_private_gitlab_registry_using_podman.html b/content/posts/2021-12-26K8S_private_gitlab_registry_using_podman.html new file mode 100644 index 0000000..43b8245 --- /dev/null +++ b/content/posts/2021-12-26K8S_private_gitlab_registry_using_podman.html @@ -0,0 +1,39 @@ +
+

K8S private gitlab registry using podman

+

+ This is based on Log in to + Docker Hub. It is just a bit different to use podman. +

+

+ First we should take a look at podman-login man page: +

man podman login
+

+

+ It will give some valueable information like the location of auth.json file. Now we can login using podman: +

podman login registry.gitlab.com
+

+

Then check the auth.json file located at ${XDG_RUNTIME_DIR}/containers/auth.json (as described + by the manual). It will contain your auth config: +

{
+	"auths": {
+		"registry.gitlab.com": {
+			"auth": "..."
+		}
+	}
+}
+

+

+ Now copy that file over to the server and register it in k8s with the following command: +


+kubectl create secret generic regcred \
+    --from-file=.dockerconfigjson=auth.json \
+    --type=kubernetes.io/dockerconfigjson
+

+

+ Once you have created you can list by kubectl get secret: +


+NAME     TYPE                                  DATA   AGE
+regcred  kubernetes.io/dockerconfigjson        1      53s
+

+
diff --git a/content/posts/Enable_NFS_on_K3S.html b/content/posts/Enable_NFS_on_K3S.html deleted file mode 100644 index 09f91e7..0000000 --- a/content/posts/Enable_NFS_on_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/Friz.box_turned_off_DHCP.html b/content/posts/Friz.box_turned_off_DHCP.html deleted file mode 100644 index 569604b..0000000 --- a/content/posts/Friz.box_turned_off_DHCP.html +++ /dev/null @@ -1,18 +0,0 @@ -
-

Friz.box turned off DHCP

-

- If you turned off your DHCP server follow these steps to connect to FritzBox settings. -
-

-

-

- On gnome turn the wired connection off on again to apply the settings. -

-

- Note: why in the hell does FritzBox 7490 require a land-line telephone to be physically factory - reset? -

-
diff --git a/content/posts/K8S_private_gitlab_registry_using_podman.html b/content/posts/K8S_private_gitlab_registry_using_podman.html deleted file mode 100644 index 43b8245..0000000 --- a/content/posts/K8S_private_gitlab_registry_using_podman.html +++ /dev/null @@ -1,39 +0,0 @@ -
-

K8S private gitlab registry using podman

-

- This is based on Log in to - Docker Hub. It is just a bit different to use podman. -

-

- First we should take a look at podman-login man page: -

man podman login
-

-

- It will give some valueable information like the location of auth.json file. Now we can login using podman: -

podman login registry.gitlab.com
-

-

Then check the auth.json file located at ${XDG_RUNTIME_DIR}/containers/auth.json (as described - by the manual). It will contain your auth config: -

{
-	"auths": {
-		"registry.gitlab.com": {
-			"auth": "..."
-		}
-	}
-}
-

-

- Now copy that file over to the server and register it in k8s with the following command: -


-kubectl create secret generic regcred \
-    --from-file=.dockerconfigjson=auth.json \
-    --type=kubernetes.io/dockerconfigjson
-

-

- Once you have created you can list by kubectl get secret: -


-NAME     TYPE                                  DATA   AGE
-regcred  kubernetes.io/dockerconfigjson        1      53s
-

-
-- cgit v1.2.3