Update module github.com/tidwall/gjson to v1.18.0 #1034
Annotations
10 warnings
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
Containers should drop 'ALL' or at least 'NET_RAW' capabilities
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
Containers should not run with allowPrivilegeEscalation in order to prevent them from gaining more privileges than their parent process
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
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
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
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
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
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/kubernetes-cost-report/templates/deployment.yaml#L30
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
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
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
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
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
Containers should be configured with a secure Seccomp profile to restrict potentially dangerous syscalls
|
|
charts/kubernetes-cost-report/templates/deployment.yaml#L1
Service Account Tokens are automatically mounted even if not necessary
|
This job succeeded
Loading