Why do I need `rbac.portForward = true;` in Helm values for viewing Hubble traffic?

[bitbloxhub]

Describe the bug

I need to set rbac.portForward = true; in Helm values to view network traffic with Hubble.

To reproduce

Steps to reproduce the behavior:

1. Try to view Hubble traffic
2. See it loop
3. Open inspector and see error like:

{
  "connected": false,
  "namespace": "kube-system",
  "serviceName": "hubble-relay",
  "error": "Failed to start port-forward: port-forward failed: error upgrading connection: unable to upgrade connection: pods \"hubble-relay-69b75d878-pvlwj\" is forbidden: User \"system:serviceaccount:radar:radar\" cannot create resource \"pods/portforward\" in API group \"\" in the namespace \"kube-system\""
}

5. Set rbac.portForward = true; in Helm values.
6. Check again and it works.

Expected behavior

To not have to set rbac.portForward = true; for Hubble traffic in the UI.

Screenshots

If applicable, add screenshots to help explain your problem.

Diagnostics (optional)

If you'd rather not include diagnostics, these basics help:

• Radar version: v1.7.6
• Kubernetes: v1.35.4+k3s1

Logs

Don't have them handy right now, could reproduce if needed.

Additional context

Deploying in-cluster via Helm. Using post-render patch with hostAliases as a workaround for #981.