HyperDX Dashboard Provisioner

[ZeynelKoca]

Summary

• Add dashboard provisioning via Helm hook Job that upserts exported HyperDX dashboard JSON directly into MongoDB on install/upgrade
• Dashboards are matched by name for idempotency (existing dashboards are updated, new ones are created, none are deleted)
• Users provide dashboard JSON inline in values or via --set-file, enabling GitOps workflows

Design decisions

• MongoDB direct insert (not API): The HyperDX external API requires a per-user access key that isn't available at deploy time. Direct MongoDB upsert avoids auth complexity and is more reliable for automated provisioning.
• Helm hook Job (not sidecar/init container): Dashboards only need provisioning once per deploy. The Job runs post-install/post-upgrade when MongoDB and the team document are guaranteed to exist, then auto-cleans up on success.
• JS file for mongosh: The provisioning script is written to a temp file to avoid shell/Helm template escaping issues with MongoDB operators ($set, $setOnInsert).
• ConfigMap as hook: Hook resources can only reference other hook resources, so the dashboard ConfigMap must also be a hook (pre-install/pre-upgrade) to be available when the post-install Job mounts it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 752d6a5

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[CLAassistant]

All committers have signed the CLA.

[ZeynelKoca]

Implements feature request #170