Helm chart hardcodes the trust-tunnel namespace

[peasewan]

Describe the bug

The Helm chart hardcodes the namespace to trust-tunnel instead of using the release namespace. This makes helm install -n <namespace> ineffective for choosing where the agent DaemonSet is installed.

Code path

In charts/trust-tunnel-agent/templates/daemonset.yaml, the template creates a fixed namespace and also pins the DaemonSet to that namespace:

apiVersion: v1
kind: Namespace
metadata:
  name: trust-tunnel
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: trust-tunnel-agent
  namespace: trust-tunnel

To Reproduce

Install the chart while specifying another namespace:

helm install trust-tunnel-agent ./charts/trust-tunnel-agent -n custom-ns --create-namespace

The DaemonSet template still targets namespace: trust-tunnel, so it is not installed into custom-ns.

Expected behavior

The chart should honor Helm's release namespace, usually by omitting metadata.namespace from namespaced resources or using {{ .Release.Namespace }} where a namespace is required.

If the chart needs to create a namespace, that should be configurable rather than hardcoded.

Additional context

values.yaml also defines values such as nameOverride, imagePullSecrets, and securityContext, but the current DaemonSet template does not appear to use them. Those may be worth wiring up as part of a chart cleanup.

Environment

• Repository: current main
• File: charts/trust-tunnel-agent/templates/daemonset.yaml