fix: helm deployment #295

Sign in to view logs

Summary
Jobs
- Analyze
Run details
- Usage
- Workflow file

Triggered via pull request November 16, 2023 10:53

PaMarzec

synchronize #81

FraunhoferISST:fix/helm-delployment

Status Success

Total duration 1m 1s

Artifacts –

kics.yml

on: pull_request

Annotations

10 warnings

[MEDIUM] Container Running With Low UID: charts/puris/charts/backend/templates/deployment.yaml#L1

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/puris/charts/frontend/templates/deployment.yaml#L1

Check if containers are running with low UID, which might cause conflicts with the host's user table.

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L176

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L45

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L45

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L176

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: frontend/docker-compose.yaml#L26

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/daps/docker-compose.yaml#L26

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L26

Incoming container traffic should be bound to a specific host interface

[MEDIUM] Container Traffic Not Bound To Host Interface: local/docker-compose.yaml#L240

Incoming container traffic should be bound to a specific host interface