You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
Configuration risks discovered in the following manifest file(s)
❌ Manifest File: /deploy/operator.yaml
Resource Name: events-operator Namespace: default
Container Name: events-operator
Overall Risk: `Medium`
Description: Ensure containers are not in `default` namespace
Vector: `AV:L/S:C/C:L/I:L/A:L/E:H`
Impact: ``
CIS Reference:
Container Name: events-operator
Overall Risk: `medium`
Description: Ensure memory usage for container is limited
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If correct memory limits are not set on each container, one process can expand its usage and cause other containers to run out of resources.`
CIS Reference: 5.10
Container Name: events-operator
Overall Risk: `medium`
Description: Ensure CPU priority is set appropriately on the container
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If you do not correctly assign CPU thresholds, the container process may run out of resources and become unresponsive. If CPU resources on the host are not constrainted, CPU shares do not place any restrictions on individual resources.`
CIS Reference: 5.11
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
GitSecure Deployment Configuration Analysis
Configuration risks discovered in the following manifest file(s)
❌ Manifest File: /deploy/operator.yaml
Resource Name: events-operator Namespace: default
The text was updated successfully, but these errors were encountered: