Mainly a brain dump for my home lab owner@DESKTOP-0V6SF20:~$ k3sup install --ip=192.168.50.76 --user=root --tls-san=192.168.50.200 --cluster --k3s-channel=stable --k3s-extra-args "--disable=traefik --disable=servicelb --disable=local-storage --node-ip=192.168.50.76" --local-path $HOME/.kube/config --context=k3s-ha --ssh-key /home/owner/

Mainly a brain dump for my home lab owner@DESKTOP-0V6SF20:~$ k3sup install --ip=192.168.50.76 --user=root --tls-san=192.168.50.200 --cluster --k3s-channel=stable --k3s-extra-args "--disable=traefik --disable=servicelb --disable=local-storage --node-ip=192.168.50.76" --local-path $HOME/.kube/config --context=k3s-ha --ssh-key /home/owner/

Not the best code but it works. To get all the header info, login while developer tools is open in chrome and then copy the request parameters. Output is consumed by telegraf #!/usr/bin/perl -w use strict; use LWP::Simple; use JSON qw( decode_json encode_json); my $url

Not the best code but it works. To get all the header info, login while developer tools is open in chrome and then copy the request parameters. Output is consumed by telegraf #!/usr/bin/perl -w use strict; use LWP::Simple; use JSON qw( decode_json encode_json); my $url

Decided to play with this learning exercise using kind (kubernetes in docker) Prereq (docker, helm2, kubectl, kind): Install docker for your distro: https://docs.docker.com/engine/install/ubuntu/ wget https://get.helm.sh/helm-v2.17.0-linux-amd64.tar.gz curl -LO "https://dl.k8s.io/release/$(curl -L -s

Decided to play with this learning exercise using kind (kubernetes in docker) Prereq (docker, helm2, kubectl, kind): Install docker for your distro: https://docs.docker.com/engine/install/ubuntu/ wget https://get.helm.sh/helm-v2.17.0-linux-amd64.tar.gz curl -LO "https://dl.k8s.io/release/$(curl -L -s

This doesn't serve any real purpose. I just like seeing trends of the tcp/udp connections to the IPFS network. Yes I get lazy at the end with a system call. #!/usr/bin/perl use warnings; use strict; my %peers; my $DEST = "INFLXUDBIP"; my $HOSTNAME = "

This doesn't serve any real purpose. I just like seeing trends of the tcp/udp connections to the IPFS network. Yes I get lazy at the end with a system call. #!/usr/bin/perl use warnings; use strict; my %peers; my $DEST = "INFLXUDBIP"; my $HOSTNAME = "

Notes for rebuilding. Wireguard has been setup in advance between the nodes and is used for internal communication on the cluster nodes: - address: PUBLIC_IP_1 user: root hostname_override: master ssh_key_path: ~/rootkey.pem internal_address: 10.10.10.1 role: - controlplane - etcd - address:

Notes for rebuilding. Wireguard has been setup in advance between the nodes and is used for internal communication on the cluster nodes: - address: PUBLIC_IP_1 user: root hostname_override: master ssh_key_path: ~/rootkey.pem internal_address: 10.10.10.1 role: - controlplane - etcd - address:

apiVersion: apps/v1 kind: Deployment metadata: name: minio labels: app: minio spec: replicas: 1 selector: matchLabels: app: minio template: metadata: labels: app: minio spec: containers: - name: minio image: minio/minio env: - name: MINIO_ACCESS_KEY value: "minio" - name: MINIO_SECRET_KEY value: "minio123"

apiVersion: apps/v1 kind: Deployment metadata: name: minio labels: app: minio spec: replicas: 1 selector: matchLabels: app: minio template: metadata: labels: app: minio spec: containers: - name: minio image: minio/minio env: - name: MINIO_ACCESS_KEY value: "minio" - name: MINIO_SECRET_KEY value: "minio123"

Not the best script in the world but it works for my purposes. Based off https://github.com/dsshafer/cacti-sb6121/blob/master/sb6121.pl #!/usr/bin/perl #use strict; my %data; my $body; my $hostname; my %opts; my $hostname = '192.168.100.1'; my $URL = 'http://'

Not the best script in the world but it works for my purposes. Based off https://github.com/dsshafer/cacti-sb6121/blob/master/sb6121.pl #!/usr/bin/perl #use strict; my %data; my $body; my $hostname; my %opts; my $hostname = '192.168.100.1'; my $URL = 'http://'

apiVersion: v1 kind: ConfigMap metadata: name: pihole-adlists data: adlists.list: | https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains http://sysctl.org/cameleon/hosts https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt https:

apiVersion: v1 kind: ConfigMap metadata: name: pihole-adlists data: adlists.list: | https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains http://sysctl.org/cameleon/hosts https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt https:

apiVersion: apps/v1 kind: Deployment metadata: name: tautulli labels: app: tautulli spec: replicas: 1 selector: matchLabels: app: tautulli template: metadata: labels: app: tautulli spec: containers: - name: tautulli image: linuxserver/tautulli env: - name: TZ value: "America/New_York" resources: limits: memory: "1Gi" requests: mem

apiVersion: apps/v1 kind: Deployment metadata: name: tautulli labels: app: tautulli spec: replicas: 1 selector: matchLabels: app: tautulli template: metadata: labels: app: tautulli spec: containers: - name: tautulli image: linuxserver/tautulli env: - name: TZ value: "America/New_York" resources: limits: memory: "1Gi" requests: mem

Now for something different. If you have a VPS provider that allows you to use a custom script after the networking layer is up, here is a quick way to install salt. On debian. wget -O - https://repo.saltstack.com/py3/debian/9/amd64/latest/SALTSTACK-GPG-KEY.pub | apt-key add

Now for something different. If you have a VPS provider that allows you to use a custom script after the networking layer is up, here is a quick way to install salt. On debian. wget -O - https://repo.saltstack.com/py3/debian/9/amd64/latest/SALTSTACK-GPG-KEY.pub | apt-key add

You could use helm or just a simple yaml since this is small. Setting up ssl is a exercise left to the reader (use cert-manager). I use a cname for the ingress rule that points to the worker node(s) apiVersion: apps/v1 kind: Deployment metadata: name: blog labels: app:

You could use helm or just a simple yaml since this is small. Setting up ssl is a exercise left to the reader (use cert-manager). I use a cname for the ingress rule that points to the worker node(s) apiVersion: apps/v1 kind: Deployment metadata: name: blog labels: app:

Had to do hacky work-arounds using the configmaps since they are read-only and I didn't want a separate config.ini file kind: ConfigMap apiVersion: v1 metadata: name: openrct2-config data: config.ini: | [general] show_fps = true currency_format = USD date_format = MM/DD/YY language = en-US temperature_format = FAHRENHEIT

Had to do hacky work-arounds using the configmaps since they are read-only and I didn't want a separate config.ini file kind: ConfigMap apiVersion: v1 metadata: name: openrct2-config data: config.ini: | [general] show_fps = true currency_format = USD date_format = MM/DD/YY language = en-US temperature_format = FAHRENHEIT

Using random pastebin examples I wrote a multi-core bcrypt. One bug to fix: after finding a match it doesn't exit early. #!/usr/bin/python3 from passlib.hash import bcrypt import os import sys import io import multiprocessing def chunks(l, n): return [l[i:i+n] for i