Read the blog post! Contains a bit more info: https://konst.fish/blog/NetBird-Reverse-Proxy-on-Kubernetes
You'll need a secret netbird-proxy-token w/ a key token obtained from running:
/go/bin/netbird-mgmt token create --name "proxy-token" (for the management container image) or
netbird-mgmt token create --name "proxy-token" (for the netbird-server container image)
Another prerequisite for this setup is cert-manager to provision the serving certificate.
Also ideally your cluster should support LoadBalancer services, otherwise you can have your ingress controller or gateway do a TLS passthrough, service will have to be changed to be ClusterIP.