Enabled override of email-domains via config (#754) #24
aimee-889create-release.yml
on: push
scan_helm
/
Kics Helm Chart Scan
25s
CodeQL
/
Analyze CodeQL
2m 4s
Linting
/
Nest Lint
1m 18s
Tests and Sonarcloud
/
Tests and Sonarcloud
14m 14s
release_helm
/
release
46s
Publish image and scan with trivy
/
Publish image
1m 24s
Publish image and scan with trivy
/
...
/
Trivy Scan
28s
Annotations
11 warnings
|
[MEDIUM] Container Running With Low UID:
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.
|
|
[MEDIUM] Container Running With Low UID:
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.
|
|
[MEDIUM] Container Running With Low UID:
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.
|
|
[MEDIUM] Container Running With Low UID:
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.
|
|
[LOW] Container Requests Not Equal To It's Limits:
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
|
|
[LOW] Container Requests Not Equal To It's Limits:
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
|
|
[LOW] Container Requests Not Equal To It's Limits:
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
|
|
[LOW] Container Requests Not Equal To It's Limits:
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
|
|
[LOW] Container Requests Not Equal To It's Limits:
charts/dbildungs-iam-server/templates/backend-deployment.yaml#L93
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#L93
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.54 MB |
sha256:973eace018b48f2c13c3bda5a48746085c5106fdd874b8470fc66ef6617b85e2
|
|