Archive
All published posts
The week ofOct 21 – Oct 27, 2024
Featured this weekLink
Note
Note
Note
The week ofOct 14 – Oct 20, 2024
Featured this weekLink
Link
Link
Note
Note
The week ofOct 7 – Oct 13, 2024
Featured this weekLink
Note
Note
Note
Note
Note
Note
Note
Note
Note
Note
Note
The week ofSep 30 – Oct 6, 2024
Featured this weekLink
Photo journal · Sep 30 – Oct 6, 2024
In pictures 1 photographs
Note
Note
Note
Note
Note
Note
Note
The week ofSep 23 – Sep 29, 2024
Featured this weekLink
Link
Note
Note
Note
The week ofSep 16 – Sep 22, 2024
Featured this weekLink
Note
Note
The week ofSep 9 – Sep 15, 2024
Featured this weekWriting
After first setting up a new k3s instance your kubeconfig file will be located in /etc/rancher/k3s/k3s.yaml.
You cans use it from here by setting $KUBECONFIG to that file.
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
Or you can copy it to ~/.kube/config
cp /etc/rancher/k3s/k3s.yaml ~/.kube/config
If you have installed k3s on a remote server and need the config on your local machine then you will need to modify the server address to reflect the remote server.
scp user@<server-ip>:/etc/rancher/k3s/k3s.yaml ~/.kube/config
Warning
only do this if you don’t already have a ~/.kube/config file, otherwise copy it to a new file and set your $KUBECONFIG env variable to use it.
Now you will need to open that file and change the server address, making sure to keep the port number.
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: ****
server: https://<server-ip>:6443
name: default
Note
Note
The week ofSep 2 – Sep 8, 2024
Featured this weekWriting
Today I gave n8n a try using podman, their docs gave me docker commands, but it ran fine on my machine using podman.
podman volume create n8n_data
podman run -it --rm --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n
Link
Note
The week ofAug 26 – Sep 1, 2024
Note
The week ofAug 19 – Aug 25, 2024
Featured this weekLink
Note
Note
Calendar data could not load. Try again.