Blog

Introduction: Welcome, everyone, to this exciting project featuring the Ulanzi TC001 Smart Pixel Clock 2882. In this series, we’ll explore the endless possibilities of this geek enthusiast’s dream device. Goals of the Project: Our primary goals with the TC001 are to harness its potential for pixelated message displays and more. We’ll achieve simultaneous follower count displays for platforms like YouTube, , Instagram TikTok and many others. The TC001 boasts a Pomodoro clock design for improved time management. Geek enthusiasts, get ready to unlock unlimited possibilities through server-based program installations. To enhance your experience, we’ll use Awtrix firmware, enabling standard Awtrix host control. Expect a hi-tech and stunning appearance with its LED full-color pixel screen. Additional Features: It’s powered by a built-in 4400mAh battery, ensuring up to 5 hours of uninterrupted usage. For convenience, use a regular 5V/1A plug for charging while in use. ...

Good day, everyone. I’m Adrian, and I’ve been navigating the dynamic world of IT since 2002, currently serving as a Quality Assurance Specialist at Fujitsu. My journey, however, began in the early 1990s with a Commodore 64, using Basic to turn it into a synthesizer, sparking my lifelong passion for IT and system security. ...

Click here: A series of articles about Ansible: Ansible+AWX Here is a video tutorial Requirements for Ansible ansible user added to the machine where aansible is installed ansible user added to sudo/wheel/admins group sudo/wheel/admins group set in /etc/sudoers to perform command with elevated privileges Create ansible playbook file: awx-install.yml 1 vim awx-install.yml And put the below content into this file. ...

Click here: A series of articles about Ansible: How to upgrade Portainer using Ansible Here is a video tutorial Requirements for Ansible: ansible user added to each remote node ansible user added to sudo/wheel/admins group sudo/wheel/admins group set in /etc/sudoers to perform command with elevated privileges Create ansible inventory 1 sudo vim /etc/ansible/hosts 1 2 3 4 5 6 7 8 9 10 all: children: portainer: hosts: AdGuard: ansible_host: 10.10.0.108 ansible_user: ansible nginx-proxy-manager: ansible_host: 10.10.0.137 ansible_user: ansible Create ansible playbook. See the video for the explanation. 1 vim portainer.yml Put the below content into this file. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 --- - name: Upgrade Portainer on AdGuard Home LXC container in Proxmox hosts: portainer become: yes tasks: - name: Stop Portainer shell: docker stop portainer - name: Remove Portainer shell: docker rm portainer - name: Create the volume that Portainer Server will use to store its database shell: docker volume create portainer_data - name: Download newest Portainer shell: sudo docker pull portainer/portainer-ce:latest - name: Run Portainer shell: docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest Run the playbook like below: 1 ansible-playbook portainer.yml Scripts and configuration files are available here:

Click here: A series of articles about Ansible: Ansible+k3s on Raspberry Pi CM4 cluster Here is a video tutorial Requirements: For Raspberry Pi / CM4 1 cgroup_memory=1 cgroup_enable=memory added to 1 /boot/cmdline.txt For Ansible ansible user added to each remote node ansible user added to sudo/wheel/admins group sudo/wheel/admins group set in /etc/sudoers to perform command with elevated privileges Create ansible inventory 1 sudo vim /etc/ansible/hosts 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 all: children: master: hosts: master-node: ansible_host: 10.10.0.112 ansible_user: ansible workers: hosts: worker-node-1: ansible_host: 10.10.0.102 ansible_user: ansible worker-node-2: ansible_host: 10.10.0.104 ansible_user: ansible Create ansible playbook. See the video for the explanation. 1 vim k3s-raspberry-cluster.yml Put the below content into this file. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 --- - name: Install K3s on Master Node hosts: master become: yes tasks: - name: Install K3s shell: curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable traefik,servicelb" K3S_KUBECONFIG_MODE="644" sh - - name: Install NGINX as ingress controller shell: kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/deploy.yaml - name: Create a patch file for NGINX ingress controller shell: cmd: | cat > ingress.yaml << EOF spec: template: spec: hostNetwork: true EOF args: executable: /bin/bash - name: patch NGINX ingress controller shell: kubectl patch deployment ingress-nginx-controller -n ingress-nginx --patch "$(cat ingress.yaml)" - name: Get K3s node token shell: cat /var/lib/rancher/k3s/server/node-token register: k3s_token delegate_to: "{{ inventory_hostname }}" - name: Install K3s on Worker Nodes hosts: workers become: yes vars: k3s_url: "https://{{ hostvars['master-node']['ansible_host'] }}:6443" k3s_token: "{{ hostvars['master-node'].k3s_token.stdout }}" tasks: - name: Join worker nodes to the cluster shell: "curl -sfL https://get.k3s.io | K3S_URL={{ k3s_url }} K3S_TOKEN={{ k3s_token }} sh -" - name: Label K3s workers on Master Node hosts: master become: yes tasks: - name: Label worker 1 shell: kubectl label nodes worker1 kubernetes.io/role=worker - name: Label worker 2 shell: kubectl label nodes worker2 kubernetes.io/role=worker Run the playbook like below: 1 ansible-playbook k3s-raspberry-cluster.yml Check on the remote k3s master node the configuration using below commands: 1 2 3 4 kubectl get nodes kubectl get pods -A kubectl get svc -A kubectl get all -A Scripts and configuration files are available here:

Here is a video tutorial Scripts and configuration files are available here: Please bear in mind that the user you are using for the installatiopn (the one that is currently logged in through ssh) has to be in sudoers group. System requirements: 4 physical CPU cores or vCPU 9 GB of free RAM, so the machine should have at least 12 GB of RAM In total 35 GB of storage space AMD64/Intel 64 Microsoft Windows 10 (version 1709 or later) MacOS 10.14 Mojave or later Red Hat Enterprise Linux/CentOS 7.5 or later This is an ephemeral cluster setup and you are not supposed to keep any important data or application inside the CRC cluster. ...

Article about known_hosts: What is known_hosts File in Linux Here is a video tutorial Scripts and configuration files are available here: Working recommended solution, but only in the environment that is not compromised. Cleanup known_hosts in /home/user/.ssh directory Run the ansible playbook with the below command: 1 ansible-playbook ssh-session.yaml Break it with ctrl+c Run the below command: 1 ./ssh-session.ssh Check the result in known_hosts 1 cat ~/.ssh/known_hosts You will see all the entries added by ssh. Run the ansible playbook with the below command one more time: 1 ansible-playbook ssh-session.yaml Type yes few times and then break it with ctrl+c Check the result in the screen. Cleanup known_hosts in /home/user/.ssh directory and then run the ansible playbook with the below command: 1 ansible-playbook ssh-session.yaml --ssh-common-args='-o StrictHostKeyChecking=no' Problem is solved. ...

All the Important Information You Need to Know About Linux’s known_hosts file A known_hosts file is a crucial component of the SSH protocol and can be found in the.ssh directory. Study up on it more. A known_hosts file can be found in your home directory’s.ssh folder along with other files. 1 2 3 4 5 6 7 adrian@rancher:~$ ls -l .ssh total 20 -rw------- 1 adrian adrian 136 Nov 10 09:37 authorized_keys -rw------- 1 adrian adrian 411 Nov 11 11:00 id_ed25519 -rw-r--r-- 1 adrian adrian 103 Nov 11 11:00 id_ed25519.pub -rw------- 1 adrian adrian 426 Nov 12 17:25 known_hosts -rw------- 1 adrian adrian 426 Nov 12 17:04 known_hosts.ansible Your private SSH key is id_ed25519 in this case.The public SSH key is pub. In SSH, profiles are created in the config file to facilitate easy connections to different servers. I specifically created it; it is not a common file. ...

Here is a video tutorial Scripts and configuration files are available here: Install ansible SLES Debian RedHat SLES | openSUSE Leap 15.4 1 sudo zypper install ansible Debian 1 sudo apt install ansible Red Hat 1 sudo dnf install ansible Create ansible directory on /etc 1 sudo mkdir /etc/ansible Create hosts file inside the /etc/ansible directory 1 sudo vim /etc/ansible/hosts and put the below content into the file ...

Here is a video tutorial Scripts and configuration files are available here: Install sshpass SLES Debian RedHat SLES | openSUSE Leap 15.4 1 sudo zypper install sshpass Debian 1 sudo apt install sshpass Red Hat 1 sudo dnf install sshpass Create a file 1 vim pass_file_ansible and place a password for the ansible user to connect to remote hosts. ...