Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add applications limits #727

Merged
merged 1 commit into from
Apr 13, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions apps/forwarder-sriov/forwarder.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 4 additions & 0 deletions apps/forwarder-vpp/forwarder.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
6 changes: 4 additions & 2 deletions apps/nsc-kernel-ponger/ponger.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 4 additions & 0 deletions apps/nsc-kernel/nsc.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 4 additions & 0 deletions apps/nsc-memif/nsc.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 2 additions & 0 deletions apps/nsc-vfio/nsc.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 4 additions & 0 deletions apps/nse-kernel/nse.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 4 additions & 0 deletions apps/nse-memif/nse.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
6 changes: 4 additions & 2 deletions apps/nse-vfio/nse.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 4 additions & 0 deletions apps/nsmgr/nsmgr.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 4 additions & 0 deletions apps/registry-k8s/registry-k8s.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 4 additions & 0 deletions apps/registry-memory/registry-memory.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down