We need to add a persistent relabeled alert rules file.

1. Improves Single Cluster

• Latency: Currently, every time a user opens the Alerting UI, the backend must query Prometheus (network call), fetch the Relabel Config (K8s call), and run a logic loop to process them.

• With Persistence: The UI simply reads a static Kubernetes resource (Like, ClusterAlertSummary). This is an instant O(1) lookup. The heavy lifting was already done by the controller when the rule changed, not when the user clicked.

2. This is Critical for Multi-Cluster

This is where the impact is massive.

• Without Persistence: To show the "All Rules" table for 1,000 clusters, this would be a very heavy task.

• With Persistence:
  • The Spoke Agent calculates the rules locally and writes them to a Resource.
  • ACM Search (which is already running) sees this Resource and indexes it into the Hub's local db.
  • The Hub UI can query the Local Search Index.
  • Result: The list loads in milliseconds, with zero network traffic to the spokes at query time.