TODO: remove service account token from ci-kubernetes-snyk-master Prow job

[tabbysable]

While moving the script out of inline YAML, we discussed whether a service account token was really needed by the Prow job: https://github.com/kubernetes/test-infra/pull/33817/files#r1866396666

For ease of troubleshooting, we plan to merge that PR as-is.

Once it's known working, it would be a nice least-privilege improvement to remove the service account token from that job, since we do not believe it needs one.

[tabbysable]

/label sig/security
/label good-first-issue

[k8s-ci-robot]

@tabbysable: The label(s) /label sig/security , /label good-first-issue cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label sig/security
/label good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tabbysable]

/sig security
/good-first-issue

[k8s-ci-robot]

@tabbysable:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/sig security
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[BenTheElder]

related: https://kubernetes.slack.com/archives/CCK68P2Q2/p1734371958722229

(it seems like probably we should move this out of the "trusted" cluster entirely?)

[andyroediger]

/assign