refactor test #5411
Annotations
11 warnings
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L22
Containers should only run as non-root user. This limits the exploitability of security misconfigurations and restricts an attacker's possibilities in case of compromise
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L34
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L38
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L53
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L22
Containers should drop 'ALL' or at least 'NET_RAW' capabilities
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L38
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L20
Service Account Tokens are automatically mounted even if not necessary
|
charts/dbildungs-iam-server/templates/redis-deployment.yaml#L22
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
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "playwright-report".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
This job succeeded
Loading