Skip to content

fix(grafana): wire orphan status-onion-service.yaml into kustomization#30

Merged
xnoto merged 1 commit intomainfrom
fix/grafana-status-onion-service
Apr 30, 2026
Merged

fix(grafana): wire orphan status-onion-service.yaml into kustomization#30
xnoto merged 1 commit intomainfrom
fix/grafana-status-onion-service

Conversation

@xnoto
Copy link
Copy Markdown
Contributor

@xnoto xnoto commented Apr 30, 2026

workloads/grafana/status-onion-service.yaml defines an OnionService for the public status dashboard but wasn't referenced from workloads/grafana/kustomization.yaml, so it was never applied. The matching tor private key (status-tor-proxy-key Secret) IS in the cluster — just unused. Adding the resource entry deploys the OnionService, which derives 7m3fv4pd5m3n24vqttmjr7x473apso2s6pfjmslildkxa5rctfikyqid.onion from that key.

After merge: kubectl get onionservice -n grafana should list status alongside grafana.

🤖 Generated with Claude Code

The file existed in the workloads/grafana directory but wasn't referenced
in resources, so the OnionService CR for the public status dashboard was
never applied. Adding it brings the onion address listed on
onion.makeitwork.cloud (7m3fv4pd5m...onion) live again.
@xnoto xnoto self-assigned this Apr 30, 2026
@xnoto xnoto merged commit 6757c16 into main Apr 30, 2026
2 checks passed
@xnoto xnoto deleted the fix/grafana-status-onion-service branch April 30, 2026 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant