Helm does not fill the waypoint-server-token secret on custom namespace

Describe the bug Launching a deploy through Helm on a custom namespace other than default works except for the provisionning of the bootstrap server token. No errors can be found as to why this is happening

Note that I'm changing the UI service type from LoadBalancer to ClusterIP

Steps to Reproduce

Bootstrap a Cluster (K3s, GKE or any other)
Deploy via helm by using the documentation provided command and adding -n waypoint --create-namespace

Expected behavior The server token should be filled

Waypoint Platform Versions Additional version and platform information to help triage the issue if applicable:

Helm CLI Version: v3.6.3
Kubernetes Version: v1.21.4-gke.2300
Waypoint CLI Version: Latest
Waypoint Server Platform and Version: 0.6.0 kubernetes

Additional context Secret

apiVersion: v1
data:
  token: ""
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: waypoint
    meta.helm.sh/release-namespace: waypoint
  creationTimestamp: "2021-10-29T08:13:27Z"
  labels:
    app.kubernetes.io/instance: waypoint
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: waypoint
  name: waypoint-server-token
  namespace: waypoint
  resourceVersion: "12662749"
  uid: c75be76e-aeea-4e58-8322-07c45f1d529d
type: Opaque

hashicorp / waypoint-helm

Helm does not fill the waypoint-server-token secret on custom namespace #12