Brian's Blog

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:

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

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

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.

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:

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/

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:

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

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:

Boot the iso  and run through the normal setup using setup-alpine . Once installed reboot and then disable the swap file: swapoff -a and remove from /etc/fstab. Finally enable cgroups rc-update add cgroups default and reboot. Then you are ready to setup k3s on

Instead of the usual ELK stack, this uses fluentd. Modified from isito docs # Namespace setup apiVersion: v1 kind: Namespace metadata: name: logging --- # Persistant volume for Elasticsearch kind: PersistentVolumeClaim apiVersion: v1 metadata: name: elasticsearch namespace: logging spec: accessModes: - ReadWriteOnce resources: requests: storage: 4Gi

If you have an existing mac and want to evaluate running OSX in Virtualbox, look here: https://medium.com/@twister.mr/installing-macos-to-virtualbox-1fcc5cf22801

So the next project to play with is k3s. All the fun of kubernetes without all the overhead or features you don't need for development https://github.com/rancher/k3s

Long time, no update. I have scrapped kubernetes for now. Way too much overkill for a simple blog. For now this lives on Google and Cloudflare. See ya in a few months.

Simple upgrade, same as the 11 -> 12 migration... [email protected]:~# kubeadm upgrade plan [preflight] Running pre-flight checks. [upgrade] Making sure the cluster is healthy: [upgrade/config] Making sure the configuration is correct: [upgrade/config] Reading configuration from the cluster... [upgrade/config] FYI:

[email protected]:~# kubeadm upgrade plan [preflight] Running pre-flight checks. [upgrade] Making sure the cluster is healthy: [upgrade/config] Making sure the configuration is correct: [upgrade/config] Reading configuration from the cluster... [upgrade/config] FYI: You can look at this config file with 'kubectl -n

No persistence (which you should really use if you want links to persist but I digress :-) ) apiVersion: apps/v1 kind: Deployment metadata: name: hastebin labels: app: hastebin spec: replicas: 1 selector: matchLabels: app: hastebin template: metadata: labels: app: hastebin spec: containers: - name:

In case you use kubernetes... kind: PersistentVolume apiVersion: v1 metadata: name: myapi-pv-volume labels: type: local spec: storageClassName: local-storage capacity: storage: 1Gi accessModes: - ReadWriteOnce hostPath: path: "/mnt/data/etcd" --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: myapi-pv-claim labels: app: myapi spec: accessModes: - ReadWriteOnce

So you can do basic auth in ingress, good to know. Use the user/password combo from mkpasswd and save to file. Then create a secret from it and change your ingress annotations kubectl create secret generic basic-auth --from-file=auth #Edit your ingress rule

NOTE: You still need a mysql or postgresql database to hold the fetched rss items. The PVC here is just to store tinyrss's config (db credentials, url, etc). --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: tinyrss labels: app: tinyrss spec: accessModes: - ReadWriteOnce resources:

https://downloads.malwarebytes.com/file/mb3/ https://download.teamviewer.com/full

If I wasn't using CloudFlare for my ssl I would switch over to LetsEncrypt and use their wildcards which are now live!

Still struggling with ideas to keep my mind busy. Consul/ETCD cluster or something else. I have no programs that need either model. I just don't know..

Odd, having issues with my certs. Cloudflare is in front but causing issues with the redirect. Not sure whether cloudflare or the nginx proxy is acting up And I am an idiot. My cert expired using "full" encryption on cloudflare. Switching to