File: rule.yml

package info (click to toggle)
scap-security-guide 0.1.78-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 114,600 kB
  • sloc: xml: 245,305; sh: 84,381; python: 33,093; makefile: 27
file content (39 lines) | stat: -rw-r--r-- 1,402 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
documentation_complete: true

title: 'Limiting Network Bandwidth in Pods'

description: |-
    Network bandwidth, SHOULD be appropriately reserved and limited.

ocil: |-
    Network bandwidth is limited at the pod level and can be determined separately according
    to incoming and outgoing network bandwidth.
    For more information about limiting network bandwidth on the pod level please refer to the Red Hat documentation:
    {{{ weblink(link="https://docs.openshift.com/container-platform/4.17/nodes/pods/nodes-pods-configuring.html#nodes-pods-configuring-bandwidth_nodes-pods-configuring") }}}

    Out of the documetation use the example for the network bandwidth configuration of a pod: 
    <pre>
    kind: Pod
    apiVersion: v1
    metadata:
      name: hello-openshift
      annotations:
        kubernetes.io/ingress-bandwidth: 2M
        kubernetes.io/egress-bandwidth: 1M
    spec:
        containers:
          - image: openshift/hello-openshift
            name: hello-openshift
    </pre>

severity: unknown

identifiers:
    cce@ocp4: CCE-87610-2
   
ocil_clause: 'Limiting Pod network bandwidth on OCP 4'

rationale: |-
    Extend pod configuration with network bandwidth annotations to prevent
    a bad actor or a malfunction in the pod to consume all the bandwidth in the cluster.
    A network bandwidth limitation on the pod level can mitigate the bearing onto the cluster.