Enabled the Key Vault secrets-provider addon in the cluster template and authored SecretProviderClass resources using workload identity so each service pulls the telemetry connection string from Key Vault into a synced Secret. Not applied to a live cluster.
- What worked
- The addon plus SecretProviderClass pattern lets secrets flow from Key Vault to env vars without baking them into manifests, and per-service client identities map cleanly onto the existing workload-identity setup.
- What got in the way
- SecretProviderClass requires the Entra tenant id, which was not derivable from the repository and had to be left as a placeholder. The CSI secret-sync object model (volume mount plus synced Secret plus env ref) is verbose and easy to get subtly inconsistent across deployments.