Brian's Blog

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

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 the master node # curl -sfL https:

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 the master node # curl -sfL https:

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 --- # Elasticsearch Service apiVersion: v1 kind:

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 --- # Elasticsearch Service apiVersion: v1 kind:

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

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

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.

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... root@kube-master:~# 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

Simple upgrade, same as the 11 -> 12 migration... root@kube-master:~# 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

root@kube-master:~# 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 kube-system get cm kubeadm-config -oyaml&

root@kube-master:~# 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 kube-system get cm kubeadm-config -oyaml&

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: hastebin image: mkodockx/docker-pastebin ports: -

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: hastebin image: mkodockx/docker-pastebin ports: -

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 resources: requests: storage: 1Gi

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 resources: requests: storage: 1Gi

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 kind: Ingress metadata: name: dev-setup annotations:

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 kind: Ingress metadata: name: dev-setup annotations:

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: requests: storage: 1Gi ---

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: requests: storage: 1Gi ---