👁️ isengard 👁️

personal ansible-tower like tool using github actions

mostly ran locally these days off my pi4 running code server

this is a living repo, master is not assumed stable

powered by github's generosity and machines i find in local dumpsters

infra

starting to run newer services in kubernetes, because i've grown tired of plain docker with compose

• applications are (usually) launched as a deployment
• when a service is added metallb provisions the service an ip address on my local network
  • optionally the service is added to the tailnet and/or given a local dns entry (usually <service>.r.ss)
• if external public access is needed an ingress record is created with a <service>.k8s.rileysnyder.dev domain
  • routed from a caddy reverse proxy acting as the entrypoint to my local network.
• longhorn for storage
• nodes are random machines that i dont have another use for at any given time, swapped out often
• manifests are under infra/k8s applied either with kubectl, k3s manifests directory, or harness (both regular deployments and gitops), because i need to try everything

secrets

using ansible vault with a password in a local file

encrypt

ansible-vault encrypt_string --vault-password-file .vault_password 'bar' --name 'foo'