Update Helm chart versions to 1.0.2 for aks, bm, and eks

[saadqbal]

• Updated Helm chart versions from 1.0.1 to 1.0.2 for all three environments (aks, bm, eks)
• Added Resource Monitor DaemonSet - New monitoring component deployed across all environments
• Enhanced RBAC configurations for resource monitoring capabilities

---

Note

Adds cluster-wide resource monitor DaemonSet with supporting RBAC across aks, bm, and eks, bumps charts to 1.0.2 (app 1.24.12), and updates docs/index.

• Helm charts
  • Bump versions to 1.0.2 and appVersion to 1.24.12 in aks/Chart.yaml, bm/Chart.yaml, eks/Chart.yaml.
  • Update repository index in index.yaml with new package entries.
• Resource monitoring
  • Add templates/resource-monitor-daemonset.yaml in aks/, bm/, eks/ defining DaemonSettracebloc-resource-monitor (tolerations for all nodes, host /proc and /sys mounts, env vars, image pull secrets, resource limits).
  • Expand RBAC in templates/rbac-rols.yaml: broaden ClusterRole resources (incl. pods/log, nodes, nodes/status, namespaces) and add ServiceAccount, ClusterRole, ClusterRoleBinding for tracebloc-resource-monitor.
• Docs
  • Add Helm Chart Verification Guide to README.md.

^{Written by Cursor Bugbot for commit c644c48. This will update automatically on new commits. Configure here.}

[cursor]

Bug: DaemonSet deploys without conditional RBAC resources

The resource-monitor-daemonset.yaml is deployed unconditionally, but it references serviceAccountName: tracebloc-resource-monitor which is only created inside the {{- if .Values.clusterRole.create }} block in rbac-rols.yaml. When .Values.clusterRole.create is false, the DaemonSet will attempt to use a non-existent ServiceAccount, causing pod creation failures. The DaemonSet needs to be wrapped in the same conditional or use a separate toggle.

Additional Locations (2)

• aks/templates/resource-monitor-daemonset.yaml#L1-L93
• bm/templates/resource-monitor-daemonset.yaml#L1-L93