Skip to content

feat: Added sample database model based on DRÄXLMAIER implementation #36

feat: Added sample database model based on DRÄXLMAIER implementation

feat: Added sample database model based on DRÄXLMAIER implementation #36

Triggered via pull request February 17, 2025 14:16
Status Success
Total duration 58s
Artifacts

kics.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
[MEDIUM] Memory Limits Not Defined: charts/industry-core-hub/templates/deployment-backend.yaml#L52
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than the designated amount of memory
[MEDIUM] Memory Requests Not Defined: charts/industry-core-hub/templates/deployment-backend.yaml#L52
Memory requests should be defined for each container. This allows the kubelet to reserve the requested amount of system resources and prevents over-provisioning on individual nodes
[MEDIUM] Service Account Token Automount Not Disabled: charts/industry-core-hub/templates/deployment-backend.yaml#L45
Service Account Tokens are automatically mounted even if not necessary
[MEDIUM] Unpinned Package Version in Apk Add: ichub-backend/Dockerfile#L37
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes
[MEDIUM] Using Unrecommended Namespace: charts/industry-core-hub/templates/deployment-backend.yaml#L24
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[MEDIUM] Using Unrecommended Namespace: charts/industry-core-hub/templates/service-backend.yaml#L23
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[MEDIUM] Using Unrecommended Namespace: charts/industry-core-hub/templates/service-backend.yaml#L24
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
[LOW] CPU Limits Not Set: charts/industry-core-hub/templates/deployment-backend.yaml#L52
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[LOW] CPU Requests Not Set: charts/industry-core-hub/templates/deployment-backend.yaml#L52
CPU requests should be set to ensure the sum of the resource requests of the scheduled Containers is less than the capacity of the node