infrastructure/addons/observability/grafana-tailscale-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: grafana-tailscale
  namespace: observability
  annotations:
    tailscale.com/hostname: grafana
    tailscale.com/tags: "tag:prod,tag:grafana"
    tailscale.com/proxy-class: infra-stable
spec:
  type: LoadBalancer
  loadBalancerClass: tailscale
  selector:
    app.kubernetes.io/name: grafana
  ports:
    - name: http
      port: 80
      protocol: TCP
      targetPort: 3000
feat: Expose Grafana, Prometheus, and Flux UI via Tailscale LoadBalancer services Replace Ansible port-forwarding + tailscale serve with direct Tailscale LB services matching the existing Rancher pattern. Each service gets its own tailnet hostname (grafana/prometheus/flux.silverside-gopher.ts.net). 2026-03-31 08:53:28 +00:00			`apiVersion: v1`
			`kind: Service`
			`metadata:`
			`name: grafana-tailscale`
			`namespace: observability`
			`annotations:`
			`tailscale.com/hostname: grafana`
fix: Reserve Tailscale service hostnames and tag exposed proxies Reserve grafana/prometheus/flux alongside rancher during rebuild cleanup so stale tailnet devices do not force -1 hostnames. Tag the exposed Tailscale services so operator-managed proxies are provisioned with explicit prod/service tags from the tailnet policy. 2026-04-18 05:48:26 +00:00			`tailscale.com/tags: "tag:prod,tag:grafana"`
feat: Expose Grafana, Prometheus, and Flux UI via Tailscale LoadBalancer services Replace Ansible port-forwarding + tailscale serve with direct Tailscale LB services matching the existing Rancher pattern. Each service gets its own tailnet hostname (grafana/prometheus/flux.silverside-gopher.ts.net). 2026-03-31 08:53:28 +00:00			`tailscale.com/proxy-class: infra-stable`
			`spec:`
			`type: LoadBalancer`
			`loadBalancerClass: tailscale`
			`selector:`
			`app.kubernetes.io/name: grafana`
			`ports:`
			`- name: http`
			`port: 80`
			`protocol: TCP`
			`targetPort: 3000`