Deploy CodeQL Scans for Kubernetes Repos

[cardi-jo]

Motivation

Currently, only a subset of repositories under in Kubernetes org are onboarded for codeQL scanning (example repo running scans via Github Runners). This issue is opened with the goal of discussing adding/enabling codeQL scanning for the remaining repos, in particular k/k.

Open Questions

• Running scans in Prow vs. Github Runners
  • Base Github Runners may not have the required hardware resources to scan all relevant repos
• Running scans as cron vs. on PRs/other events of interest
  • Would likely need to run as cron at least initially

[cardi-jo]

/assign

[heineza]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale