Wayan jimmy wayanjimmy

# note that helm tempates are converted into yaml and a kubectl apply is run on the yaml object, ie `helm ls` will not show anything

# TODO move these to config files
settings = {
  "start_kind": True,
  "preload_images_for_kind": True,
  "deploy_metallb": True,
  "deploy_ambassador_api": False,
  "deploy_ambassador_edge_gateway": False,

Save these files as ~/.config/systemd/user/some-service-name.*

Run this now and after any modifications: systemctl --user daemon-reload

Try out the service (oneshot): systemctl --user start some-service-name

Check logs if something is wrong: journalctl -u --user-unit some-service-name

Start the timer after this user logs in: systemctl --user enable --now some-service-name.timer

Prerequisites

kubectl

Install the required tools for deploying and controlling k3s.

Installation Docs:

# Download
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"

Cloudflare Warp client on Fedora/EL

sudo dnf config-manager --add-repo https://pkg.cloudflareclient.com/cloudflare-warp-ascii.repo
sudo dnf install cloudflare-warp

/etc/systemd/resolved.conf

	# By default the ssh-agent service is disabled. Configure it to start automatically.
	# Make sure you're running as an Administrator.
	Get-Service ssh-agent \| Set-Service -StartupType Automatic

	# Start the service
	Start-Service ssh-agent

	# This should return a status of Running
	Get-Service ssh-agent