2018-11-27 18:52:17 -05:00
|
|
|
// Module included in the following assemblies:
|
|
|
|
|
//
|
|
|
|
|
// * nodes/nodes-cluster-overcommit.adoc
|
2020-05-19 14:47:58 -04:00
|
|
|
// * post_installation_configuration/node-tasks.adoc
|
2018-11-27 18:52:17 -05:00
|
|
|
|
2019-05-13 08:55:00 +10:00
|
|
|
[id="nodes-cluster-overcommit-project-disable_{context}"]
|
2018-11-27 18:52:17 -05:00
|
|
|
= Disabling overcommitment for a project
|
|
|
|
|
|
2019-06-20 14:22:25 -04:00
|
|
|
When enabled, overcommitment can be disabled per-project.
|
2018-11-27 18:52:17 -05:00
|
|
|
For example, you can allow infrastructure components to be configured independently of overcommitment.
|
|
|
|
|
|
|
|
|
|
.Procedure
|
|
|
|
|
|
|
|
|
|
To disable overcommitment in a project:
|
|
|
|
|
|
|
|
|
|
. Edit the project object file
|
|
|
|
|
|
|
|
|
|
. Add the following annotation:
|
|
|
|
|
+
|
2020-08-05 21:30:49 -04:00
|
|
|
[source,yaml]
|
2018-11-27 18:52:17 -05:00
|
|
|
----
|
|
|
|
|
quota.openshift.io/cluster-resource-override-enabled: "false"
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
. Create the project object:
|
|
|
|
|
+
|
2020-08-05 21:30:49 -04:00
|
|
|
[source,terminal]
|
2018-11-27 18:52:17 -05:00
|
|
|
----
|
2019-02-25 19:08:28 -05:00
|
|
|
$ oc create -f <file-name>.yaml
|
2018-11-27 18:52:17 -05:00
|
|
|
----
|
