Disclaimer: this step-by-step GIST has been created with no guarantees, I may have missed some steps because of distraction or chiptune improvised on-chair-dancing, so be patient and let me know if I must add or fix something.
This is the way for living long and prospering!
Download and install Raspberry Imager: https://www.raspberrypi.org/software/
| <html> | |
| <head> | |
| <script type="text/javascript" src="/jquery.min.js"></script> | |
| <title>Mime type checker</title> | |
| <script> | |
| $(function () { | |
| var result = $('div#result'); | |
| if (window.FileReader && window.Blob) { | |
| $('span#submit').click(function () { | |
| var files = $('input#file').get(0).files; |
| apiVersion: v1 | |
| kind: Pod | |
| metadata: | |
| name: ubuntu | |
| labels: | |
| app: ubuntu | |
| spec: | |
| containers: | |
| - image: ubuntu | |
| command: |
| apiVersion: v1 | |
| kind: ConfigMap | |
| metadata: | |
| name: pihole-config | |
| data: | |
| WEBPASSWORD: pihole | |
| TZ: 'Asia/Ho_Chi_Minh' | |
| DNS1: 1.1.1.1 | |
| DNS2: 1.0.0.1 |
Today I tried to setup a small Kubernetes cluster on top of 3 Raspberry Pi 4 (4GB Memory). Here is the steps to install the cluster.
I have 3 Raspberry Pi 4 stacked with PoE headers and connected to a PoE switch at home. The are connected to Internet through a home router. All Pis are equipped with a 64GB Samsung SDXC card flushed with Ubuntu 20.04 image.
| #!/bin/bash -x | |
| # make_arm64_rpi_kernel_debs.sh | |
| # Builds arm64 debian packages from the CURRENT rpi firmware repository kernel which is installed by: | |
| # sudo rpi-update | |
| # This runs on an arm64 host with arm64 compilation tools... | |
| # or with some sort of cross-compilation setup. | |
| # Debs are put in $workdir/build | |
| # | |
| # This will NOT work in Raspbian unless you have an arm64 compilation | |
| # environment setup. Appears to work on |
Install ffmpeg
brew install ffmpeg
Download file through url, like this:
ffmpeg -protocol_whitelist file,http,https,tcp,tls,crypto -i "http://url-file.domain.m3u8" -c copy video.mp4
Alright! I'd like to apologize for the inactivity for over a year. Very embarrassingly, I totally dropped the good habit. Anyways, today I'd like to share a not so advanced and much shorter walkthrough on how to upgrade Kubernetes with kops.
At Buffer, we host our own k8s (Kubernetes for short) cluster on AWS EC2 instances since we started our journey before AWS EKS. To do this effectively, we use kops. It's an amazing tool that manages pretty much all aspects of cluster management from creation, upgrade, updates and deletions. It never failed us.
Okay, upgrading a cluster always makes people nervous, especially a production cluster. Trust me, I've been there! There is a saying, hope is not a strategy. So instead of hoping things will go smoothly, I always have bias that shit will hit the fan if you skip testing. Plus, good luck explaining to people
| kubectl delete "$(kubectl api-resources --namespaced=true --verbs=delete -o name | tr "\n" "," | sed -e 's/,$//')" --all |
| #!/bin/bash | |
| #qemu-img create -f qcow2 disk.qcow2 20G | |
| #qemu-img create -f qcow2 varstore.img 128M | |
| debian_iso=debian-9.6.0-arm64-xfce-CD-1.iso | |
| qemu-system-aarch64 -smp cpus=6 -M virt -cpu max -m 2G -nographic \ | |
| -drive file=QEMU_EFI.img,if=pflash,format=raw \ | |
| -drive file=varstore.img,if=pflash \ | |
| -drive file=disk.qcow2,if=virtio \ | |
| -drive file=$debian_iso,if=virtio,format=raw |