Add applications limits

Signed-off-by: Vladimir Popov <vladimir.popov@xored.com>
networkservicemesh · Apr 6, 2021 · 48f4c8c · 48f4c8c
1 parent 75a5b47
commit 48f4c8c
Show file tree

Hide file tree

Showing 12 changed files with 46 additions and 4 deletions.
diff --git a/apps/forwarder-sriov/forwarder.yaml b/apps/forwarder-sriov/forwarder.yaml
@@ -44,6 +44,10 @@ spec:
               mountPath: /host/sys/fs/cgroup
             - name: vfio
               mountPath: /host/dev/vfio
+          resources:
+            limits:
+              memory: 40Mi
+              cpu: 200m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/forwarder-vpp/forwarder.yaml b/apps/forwarder-vpp/forwarder.yaml
@@ -39,6 +39,10 @@ spec:
               readOnly: true
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
+          resources:
+            limits:
+              memory: 400Mi
+              cpu: 500m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/nsc-kernel-ponger/ponger.yaml b/apps/nsc-kernel-ponger/ponger.yaml
@@ -26,10 +26,12 @@ spec:
             - name: scripts
               mountPath: /root/scripts
               readOnly: true
-          # We don't actually need resources for ponger, but we need to be sure that it is going to be deployed on the
-          # correct node.
+          # We don't actually need SR-IOV resources for ponger, but we need to be sure that it is going to be deployed
+          # on the correct node.
           resources:
             limits:
+              memory: 10Mi
+              cpu: 10m
               # We expect SR-IOV forwarders on the nodes to be configured:
               # master - provides PCI functions targeted to the worker.domain/10G
               # worker - provides PCI functions targeted to the master.domain/10G

diff --git a/apps/nsc-kernel/nsc.yaml b/apps/nsc-kernel/nsc.yaml
@@ -32,6 +32,10 @@ spec:
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
               readOnly: true
+          resources:
+            limits:
+              memory: 15Mi
+              cpu: 100m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/nsc-memif/nsc.yaml b/apps/nsc-memif/nsc.yaml
@@ -34,6 +34,10 @@ spec:
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
               readOnly: true
+          resources:
+            limits:
+              memory: 400Mi
+              cpu: 500m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/nsc-vfio/nsc.yaml b/apps/nsc-vfio/nsc.yaml
@@ -48,6 +48,8 @@ spec:
               mountPath: /dev/vfio
           resources:
             limits:
+              memory: 15Mi
+              cpu: 100m
               # We expect SR-IOV forwarders on the nodes to be configured:
               # master - provides PCI functions targeted to the worker.domain/10G
               # worker - provides PCI functions targeted to the master.domain/10G

diff --git a/apps/nse-kernel/nse.yaml b/apps/nse-kernel/nse.yaml
@@ -34,6 +34,10 @@ spec:
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
               readOnly: true
+          resources:
+            limits:
+              memory: 20Mi
+              cpu: 100m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/nse-memif/nse.yaml b/apps/nse-memif/nse.yaml
@@ -34,6 +34,10 @@ spec:
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
               readOnly: true
+          resources:
+            limits:
+              memory: 400Mi
+              cpu: 500m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/nse-vfio/nse.yaml b/apps/nse-vfio/nse.yaml
@@ -50,10 +50,12 @@ spec:
               readOnly: true
             - name: nsm
               mountPath: /var/lib/networkservicemesh
-          # We don't actually need resources for NSE, but we need to be sure that it is going to be deployed on the
-          # correct node.
+          # We don't actually need SR-IOV resources for NSE, but we need to be sure that it is going to be deployed
+          # on the correct node.
           resources:
             limits:
+              memory: 20Mi
+              cpu: 100m
               # We expect SR-IOV forwarders on the nodes to be configured:
               # master - provides PCI functions targeted to the worker.domain/10G
               # worker - provides PCI functions targeted to the master.domain/10G

diff --git a/apps/nsmgr/nsmgr.yaml b/apps/nsmgr/nsmgr.yaml
@@ -44,6 +44,10 @@ spec:
               readOnly: true
             - name: nsm-socket
               mountPath: /var/lib/networkservicemesh
+          resources:
+            limits:
+              memory: 60Mi
+              cpu: 200m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/registry-k8s/registry-k8s.yaml b/apps/registry-k8s/registry-k8s.yaml
@@ -36,6 +36,10 @@ spec:
           volumeMounts:
             - name: spire-agent-socket
               mountPath: /run/spire/sockets
+          resources:
+            limits:
+              memory: 40Mi
+              cpu: 100m
       volumes:
         - name: spire-agent-socket
           hostPath:

diff --git a/apps/registry-memory/registry-memory.yaml b/apps/registry-memory/registry-memory.yaml
@@ -31,6 +31,10 @@ spec:
           volumeMounts:
             - name: spire-agent-socket
               mountPath: /run/spire/sockets
+          resources:
+            limits:
+              memory: 20Mi
+              cpu: 100m
       volumes:
         - name: spire-agent-socket
           hostPath: