C0: point tailscale-operator base mirror fetch at tailnet forge

The public forge.eblu.me now black-holes /mirrors/ at the Fly edge
(AI-scraper mitigation), so the in-cluster ArgoCD repo-server got a 403
fetching the upstream operator manifest — leaving tailscale-operator and
tailscale-operator-ringtail in Unknown sync. Use forge.ops.eblu.me.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-06-04 12:39:50 -07:00
commit 02ea1cc72a
2 changed files with 5 additions and 1 deletions

View file

@ -6,8 +6,11 @@ namespace: tailscale
# Upstream Tailscale operator manifest from forge mirror. # Upstream Tailscale operator manifest from forge mirror.
# To upgrade: update the ref in the URL AND the newTag below. # To upgrade: update the ref in the URL AND the newTag below.
# Must use the tailnet host forge.ops.eblu.me — the public forge.eblu.me
# black-holes /mirrors/ at the Fly edge (AI-scraper mitigation), which the
# in-cluster ArgoCD repo-server would otherwise hit and fail with a 403.
resources: resources:
- https://forge.eblu.me/mirrors/tailscale/raw/tag/v1.94.2/cmd/k8s-operator/deploy/manifests/operator.yaml - https://forge.ops.eblu.me/mirrors/tailscale/raw/tag/v1.94.2/cmd/k8s-operator/deploy/manifests/operator.yaml
- proxyclass.yaml - proxyclass.yaml
- dnsconfig.yaml - dnsconfig.yaml

View file

@ -0,0 +1 @@
Fixed the `tailscale-operator` and `tailscale-operator-ringtail` ArgoCD apps showing `Unknown` sync status. Their shared base kustomization fetched the upstream operator manifest from the public `forge.eblu.me/mirrors/...`, which the AI-scraper mitigation now black-holes (403). Pointed the remote resource at the tailnet host `forge.ops.eblu.me` instead, which the in-cluster repo-server can reach.