Route runner polling through internal forge.ops.eblu.me

The k8s and ringtail runners were hitting forge.eblu.me (fly.io proxy)
for every FetchTask poll (~every 2s), round-tripping through the public
internet unnecessarily. Use forge.ops.eblu.me (Caddy on indri, tailnet)
for infrastructure workloads.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-03-03 10:33:40 -08:00
commit 82884436df
2 changed files with 2 additions and 2 deletions

View file

@ -25,7 +25,7 @@ spec:
- name: DOCKER_HOST - name: DOCKER_HOST
value: tcp://localhost:2375 value: tcp://localhost:2375
- name: FORGEJO_URL - name: FORGEJO_URL
value: "https://forge.eblu.me" value: "https://forge.ops.eblu.me"
- name: RUNNER_NAME - name: RUNNER_NAME
value: "k8s-runner" value: "k8s-runner"
- name: RUNNER_LABELS - name: RUNNER_LABELS

View file

@ -496,7 +496,7 @@ in
instances.nix_container_builder = { instances.nix_container_builder = {
enable = true; enable = true;
name = "ringtail-nix-builder"; name = "ringtail-nix-builder";
url = "https://forge.eblu.me"; url = "https://forge.ops.eblu.me";
tokenFile = "/etc/forgejo-runner/token.env"; tokenFile = "/etc/forgejo-runner/token.env";
labels = [ "nix-container-builder:host" ]; labels = [ "nix-container-builder:host" ];
hostPackages = with pkgs; [ hostPackages = with pkgs; [