Hey @sam-ulrich1 I'm looking at this now. I don't yet know if you're having a similar problem as another user did a couple of days ago (link), but it does sound suspiciously similar. Both cases involved pieces of the router's identity in Kubernetes. I suspect the other issue was caused by skipping Helm chart versions during an upgrade, and the problem didn't recur with a fresh install.
Are you seeing this on a fresh install?
Let's check for obvious problems with kubectl get events --all-namespaces --watch (or narrow to Ziti namespace) while creating the Helm release for the Ziti Router, and kubectl describe pods --selector app.kubernetes.io/component=ziti-router after creating the release.
Where was that MountVolume.SetUp error emitted?
Does that expected K8s Secret exist in any namespace?
I assume <TOKEN> is a redaction, and the token was valid. I often check tokens with https://jwt.io if not sensitive, or this Python script if I need to keep the token offline.