# https://docs.k3s.io/quick-start
curl -sfL https://get.k3s.io | sh -optionally setup your kubectl config
mkdir -p ~/.kube
sudo cp /etc/rancher/k3s/k3s.yaml ~/.kube/config
sudo chown $USER:$USER ~/.kube/configand set the KUBECONFIG env var in your shell profile
export KUBECONFIG=$HOME/.kube/configsudo apt install nfs-kernel-server
# if you want to adjust the nfs dir, reflect the changes in the apps' yamls too
sudo mkdir -p /mnt/nfs
# populate your exports with something like this, you might want to adjust the IP range
sudo echo "/mnt/nfs 192.168.2.0/24(rw,sync,no_subtree_check,no_root_squash)" >> /etc/exports
# and the ownership
sudo chown -R nobody:nogroup /mnt/nfs
# and the permissions as well.
sudo chmod -R 755 /mnt/nfs
# apply configuration and start service
sudo exportfs -a
sudo systemctl restart nfs-kernel-server
sudo systemctl enable nfs-kernel-serverhttps://argo-cd.readthedocs.io/en/stable/getting_started/
Upon installing the cert-manager, I'm usually having some trouble with the cainjector health at some point. A restart of the node helps, not sure why.
To set up ESO, the auth secret for the provider (Infisical) needs to be created. If you choose a different provider, adjust the external-secret chart accordingly.
kubectl create secret generic infisical-auth-credentials \
--from-literal=clientId=<your-client-id-here> \
--from-literal=clientSecret=<your-client-secret-here> \
--namespace=default