PR#1306: communishift: set default resource limits for pods - fedora-infra/ansible

fedora-infra / ansible

#1306 communishift: set default resource limits for pods

Merged a year ago by kevin. Opened a year ago by darknao.

fedora-infra/ darknao/ansible communishift into main

communishift: set default resource limits for pods

Francois Andrieu • a year ago

7e979cb

roles/communishift/tasks/create-limit-range.yml

file added

+21

		`@@ -0,0 +1,21 @@`
		`+ ---`
		`+ - name: Create a k8s LimitRange`
		`+ community.okd.k8s:`
		`+ api_key: "{{ communishift_ocp_api_token }}"`
		`+ host: "{{ communishift_ocp_api_host }}"`
		`+ state: present`
		`+ definition:`
		`+ apiVersion: v1`
		`+ kind: LimitRange`
		`+ metadata:`
		`+ name: "{{ communishift_project_name }}-limitrange"`
		`+ namespace: "{{ communishift_project_name }}"`
		`+ spec:`
		`+ limits:`
		`+ - default:`
		`+ cpu: 500m`
		`+ memory: 500Mi`
		`+ defaultRequest:`
		`+ cpu: 100m`
		`+ memory: 100Mi`
		`+ type: Container`

roles/communishift/tasks/main.yml

file modified

		`@@ -12,3 +12,4 @@`
		`- include_tasks: create-role.yml`
		`- include_tasks: create-role-binding.yml`
		`- include_tasks: create-resource-quota.yml`
		`+ - include_tasks: create-limit-range.yml`

darknao commented a year ago

Once a resource quota is set for a namespace, kube will refuse to
schedule any pod without limits set, including build pod.
This can be difficult to figure out unless you know where to look, and
can be challenging for new openshift/kubernetes users.
Setting a default limit would, at least, avoid the non-schedulable
issue.