Can't use mirrord because luck of k8s permissions/auto attach

[assapir]

Trying to run mirrord (via VSCode extension), I am getting the following error:

mirrord error: Failed to create mirrord-agent: ApiError: jobs.batch is forbidden: 
User "..." cannot create resource "jobs" in API group "batch" in the namespace "default": 
Forbidden (ErrorResponse { status: "Failure", message: "jobs.batch is forbidden: User \"...\" cannot create resource \"jobs\" in API group \"batch\" in the namespace \"default\"", reason: "Forbidden", code: 403 })

Not sure why it needs to run a k8s job, but it doesn't say anywhere I could find (not in the readme, nor in the FAQ) that the user is required to have such permission. In practice, it crashes the debug session.

Also, the pop-up to select which pod to connect doesn't show up when running a node process and debugging via auto-attach

[eyalb181]

Hey @assapir ,

The mirrord Agent runs as a job, which is why the permissions are required (only in the mirrord OSS, in mirrord for Teams these permissions aren't needed for end users). You're right about the documentation though, we need to add that.

Regarding Node, so you're toggling on mirrord, running the process, and the pop-up doesn't show? It's supposed to show on process start-up so the auto-attach later shouldn't be relevant. If this is the case, could you open a bug report and attach layer logs?

[assapir]

Yes. That the case - the debug session is starting using auto attach, but no pop up is shown.
We don't start the node process directly but via a small cli (also in node) that watch for changes (among other things). Can it be related?

How can I get the layer logs?

[eyalb181]

It could be related, but we usually handle this sort of thing.

Go to Issues -> New Issue -> Bug Report and there are instructions in the template.

[assapir]

#3556

Also added more details.
I can share the startup script in private if needed.

Thanks for all the help, appreciated!