Disk) quota imposed on a per-namespace basis in k8s cluster
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	Jprorama
	Aug 14 2017, 2:09 PM

Description

This is a place holder task to serve as a reference point for info and discussion of resource quotas for tools in Kubernetes cluster.

It stems from a note in the k8s Admin docs on the desire to provide this feature to manage contention between tools using the k8s backend:

There will be a resource based (CPU/IO/Disk) quota imposed on a per-namespace basis at some point in the future. "

Search of phabricator suggests no general task for k8s resource quotas appears to exist yet.

One use-case motivating resource quota discussions for Toolforge tools is PAWS. Migration of PAWS to a dedicated k8s cluster (T167086) is a possible solution in this particular case.

Some additional quota commentary and actions related to tool startup are available in T169954#3427978

Related Objects

Mentioned Here: T167086: Consider moving PAWS to its own Cloud VPS project, rather than using instances inside Toolforge
T169954: Performance and OOM issues with Flask tool on Kubernetes

Event Timeline

Jprorama created this task.Aug 14 2017, 2:09 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 14 2017, 2:09 PM

Jprorama updated the task description. (Show Details)Aug 14 2017, 2:25 PM

K8s quotas are implemented with a per-namespace ResourceQuota object. See k8s quota documentation.

Jprorama added a project: Toolforge.Aug 14 2017, 3:24 PM

bd808 closed this task as a duplicate of T234702: Review and establish configurable quotas for users in the new Kubernetes cluster.Dec 17 2019, 5:34 AM

Resource based (CPU/IO/Disk) quota imposed on a per-namespace basis in k8s clusterClosed, DuplicatePublicActions

Description

Related Objects

Event Timeline

Resource based (CPU/IO/Disk) quota imposed on a per-namespace basis in k8s cluster
Closed, DuplicatePublic
Actions