Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, github/codeql-action/upload-sarif@28deaeda66b76a05916b6923827895f2b14ab387. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Image Pull Policy of the container must be defined and set to Always

Image Pull Policy of the container must be defined and set to Always

Deployments should be assigned with a PodDisruptionBudget to ensure high availability

Cronjobs must have a configured deadline, which means the attribute 'startingDeadlineSeconds' must be defined

Service Account Tokens are automatically mounted even if not necessary

Service Account Tokens are automatically mounted even if not necessary

Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls

Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls

Check if containers are running with low UID, which might cause conflicts with the host's user table.