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

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

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

Service Account Tokens are automatically mounted even if not necessary

Service Account Tokens are automatically mounted even if not necessary

Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.

Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.

Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively