Skip to content

SPSH-1291: LdapPersonEntries have objectClass posixAccount (#740) #22

SPSH-1291: LdapPersonEntries have objectClass posixAccount (#740)

SPSH-1291: LdapPersonEntries have objectClass posixAccount (#740) #22

Triggered via push November 7, 2024 15:54
Status Success
Total duration 17m 19s
Artifacts 1
scan_helm  /  Kics Helm Chart Scan
29s
scan_helm / Kics Helm Chart Scan
CodeQL  /  Analyze CodeQL
1m 41s
CodeQL / Analyze CodeQL
Linting  /  Nest Lint
1m 17s
Linting / Nest Lint
Tests and Sonarcloud  /  Tests and Sonarcloud
14m 47s
Tests and Sonarcloud / Tests and Sonarcloud
release_helm  /  release
45s
release_helm / release
Publish image and scan with trivy  /  Publish image
1m 22s
Publish image and scan with trivy / Publish image
Publish image and scan with trivy  /  pre_scan
0s
Publish image and scan with trivy / pre_scan
Publish image and scan with trivy  /  ...  /  Trivy Scan
36s
Publish image and scan with trivy / Trivy scan for uploaded image / Trivy Scan
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
[MEDIUM] Container Running With Low UID: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L69
Check if containers are running with low UID, which might cause conflicts with the host's user table.
[MEDIUM] Container Running With Low UID: 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.
[MEDIUM] Container Running With Low UID: 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.
[MEDIUM] Container Running With Low UID: 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.
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-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
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-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
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L91
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
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-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
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-deployment.yaml#L91
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
[LOW] Container Requests Not Equal To It's Limits: charts/dbildungs-iam-server/templates/backend-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
release_helm / release
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/setup-helm@5119fcb9089d432beecbf79bb2c7915207344b78. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size Digest
test-artifacts Expired
1.52 MB
sha256:bbbfe7da9763268a25c2fed811b0e507f6d6963e458a35737ad8162e790fbd49