Files
configpolicy/group_vars/private-oci-registry.yml
Dustin C. Hatch 719be9a4e9 Deploy Radarr, Sonarr, Prowlarr on file0.p.b
I had originally intended to deploy Radarr, Sonarr, and Prowlarr on
Kubernetes.  Unfortunately, this turned out to be problematic, as I
would need a way to share the download directory between Radarr/Sonar
and Aria2, and the media directory between Radarr/Sonarr and Jellyfin.
The only way I could fathom to do this would be to expose both
directories via NFS and mount that share into the pods.  I decided this
would be too much of a hassle for no real gain, at least not in the
short term.  Instead, it makes more sense to deploy the *arr suite on
the same server as Aria2 and Jellyfin, which is essentially what the
community expects.

The recommended images for deploying the applications in containers are
pretty crappy. I didn't really want to mess with trying to get the
them to work natively on Fedora, nor deal with installing them from
tarballs with Ansible, so I created my own Debian-based container images
for them and deployed those via Podman+Quadlet.  These images are
published to the _Packages_ organization in Gitea, which is not public
and requires authentication.  We can use the Kubernetes Secret to obtain
the authentication token to use to pull the image.
2025-12-03 23:05:21 -06:00

17 lines
337 B
YAML

oci_registry_auth_secret: >-
{{ lookup(
"cache",
"kubernetes.core.k8s",
kind="Secret",
namespace="default",
resource_name="imagepull-gitea"
) }}
oci_registry_auth: >-
{{ (oci_registry_auth_secret
.data[".dockerconfigjson"]
| b64decode
| from_json
).auths["git.pyrocufflink.net"]
}}