feat: add e2e setup workflow #47
ds-jhartmannAnnotations
10 warnings
|
[MEDIUM] Container Running With Low UID:
.github/configs/deploy.yaml#L499
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
[MEDIUM] Memory Limits Not Defined:
.github/configs/deploy.yaml#L611
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 Limits Not Defined:
.github/configs/deploy.yaml#L558
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 Limits Not Defined:
.github/configs/deploy.yaml#L463
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:
.github/configs/deploy.yaml#L558
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] Memory Requests Not Defined:
.github/configs/deploy.yaml#L611
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] RBAC Roles with Read Secrets Permissions:
.github/configs/deploy.yaml#L163
Roles and ClusterRoles with get/watch/list RBAC permissions on Kubernetes secrets are dangerous and should be avoided. In case of compromise, attackers could abuse these roles to access sensitive data, such as passwords, tokens and keys
|
|
[MEDIUM] RBAC Roles with Read Secrets Permissions:
.github/configs/deploy.yaml#L59
Roles and ClusterRoles with get/watch/list RBAC permissions on Kubernetes secrets are dangerous and should be avoided. In case of compromise, attackers could abuse these roles to access sensitive data, such as passwords, tokens and keys
|
|
[MEDIUM] RBAC Roles with Read Secrets Permissions:
.github/configs/deploy.yaml#L140
Roles and ClusterRoles with get/watch/list RBAC permissions on Kubernetes secrets are dangerous and should be avoided. In case of compromise, attackers could abuse these roles to access sensitive data, such as passwords, tokens and keys
|
|
[MEDIUM] Service Account Token Automount Not Disabled:
.github/configs/deploy.yaml#L10
Service Account Tokens are automatically mounted even if not necessary
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
kicsResults.json
Expired
|
10 KB |
|