Can't generate kubeconfig file for remote cluster integration using the authentik-remote-cluster helmchart

[CookieDude24]

Describe the bug
The helm chart doesn't create the nessescary secret so it defaults to "authentik-authentik-remote-cluster" secret which also doesn't exist. Thus I can't fill in the variables in the kubeconfig file that the helm chart outputs.

To Reproduce
Steps to reproduce the behavior:

1. Create K8s Cluster with k3s v1.30.0+k3s1
2. Install authentik-remote-cluster helmchart using this command: helm install authentik authentik/authentik-remote-cluster
3. After succesful helmchart installlation execute following commands:
   KUBE_API=$(kubectl config view --minify --output jsonpath="{.clusters[*].cluster.server}")
NAMESPACE=default
SECRET_NAME=$(kubectl get serviceaccount authentik-authentik-remote-cluster -o jsonpath='{.secrets[0].name}' 2>/dev/null || echo -n "authentik-authentik-remote-cluster")
KUBE_CA=$(kubectl -n $NAMESPACE get secret/$SECRET_NAME -o jsonpath='{.data.ca\.crt}')
KUBE_TOKEN=$(kubectl -n $NAMESPACE get secret/$SECRET_NAME -o jsonpath='{.data.token}' | base64 --decode)
   The last two throw the following error:
   Error from server (NotFound): secrets "authentik-authentik-remote-cluster" not found

Expected behavior
The secret/serviceaccount being generated.

Screenshots
Note the non-existance of the required secret and the service account.

Logs
output of helm status authentik

Version and Deployment (please complete the following information):

• authentik version: 2024.4.2
• Deployment: authentik: docker-compose, remote-outpost: helm

[CookieDude24]

I fixed the problem by using ArgoCD to install the helmchart. Though the name of the generated secret is authentik-remote-clusters. As a sanity check I tried the installation with helm again, this time explicitly setting the newest version using the option --version 2.0.0, but it still didn't work.