fix sonarcloud issues #7768
Annotations
12 warnings
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L71
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/cronjob.yaml#L22
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
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
|
|
Scan with kics:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L24
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/
|
Loading