Document how to configure allowed running workspaces count

Describe the bug

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Expected behavior

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Installation method

• chectl
• che-operator
• minishift-addon
• I don’t know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Eclipse Che Logs

Additional context

[hari1992-web]

@hari1992-web the way how you configure it depends on the way you deployed Che: Helm kubectl patch configmap che --patch “{"spec":{"data":{"CHE_LIMITS_USER_WORKSPACES_RUN_COUNT": "-1"}}}” --type=merge -n che kubectl rollout restart deployment/che -n che

Operator: kubectl patch checluster/eclipse-che --patch “{"spec":{"server":{"customCheProperties": {"CHE_LIMITS_USER_WORKSPACES_RUN_COUNT": "-1"}}}}” --type=merge -n che

P.S. There is -1 - not limited, but feel free to assign any value. It must be documented!

Thanku so much Its working fine

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.