From f8c1a7053324c19b68f78f0e1dd17e068d3fb66d Mon Sep 17 00:00:00 2001 From: Anatolii Bazko Date: Tue, 22 Oct 2024 10:02:48 +0200 Subject: [PATCH] Update _posts/2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc Co-authored-by: David Kwon --- .../2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc b/_posts/2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc index 20a7b7e..34bf769 100644 --- a/_posts/2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc +++ b/_posts/2024-10-28-boosting-cde-security-on-kubernetes-cluster.adoc @@ -17,7 +17,7 @@ As organizations transition to cloud-native development, maintaining control, se Effective resource management is critical in cloud-based environments, as uncontrolled workspace development can quickly deplete resources and degrade system performance. To mitigate this risk, Eclipse Che now has a functionality that restricts the amount of running workspaces per cluster. -Administrators can use this feature to limit the amount of workspaces that can run at the same time, reducing resource misuse, supports fair allocation of resources among teams, and increasing overall efficiency. +Administrators can use this feature to limit the amount of workspaces that can run at the same time, reducing resource misuse, supporting fair allocation of resources among teams, and increasing overall efficiency. In the example below, we set the maximum number of running workspaces per cluster to 20: