CHE_LIMITS_USER_WORKSPACES_COUNT Does not appear work in Che7.11.0

[donenocode]

Describe the bug

Setting 'CHE_LIMITS_USER_WORKSPACES_COUNT=0' does not appear to have any effect.
User can continue to create workspaces outside of organizations.

Che version

• latest
• nightly
• other:7.11.0

Steps to reproduce

1. Deploy Che multiuser to Kubernetes using chectl
2. Add 'CHE_LIMITS_USER_WORKSPACES_COUNT=0' to 'che' configmap
3. Rollout restart Che server deployment
4. Add user(s) to keycloak
5. Login as a user
6. Create workspace not in an organization

Expected behavior

User should be prevented from creating workspace

Runtime

• kubernetes

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.1", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", Platform:"linux/amd64"}

Installation method

• chectl
  chectl server:start --platform=k8s -m -s --chenamespace=che-test --domain=<DOMAIN HERE>

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: Ubuntu 18.04 vSphere VM's

Additional context

I have a Che 6.x multi user installation with 186 developers and this config option works as expected.
Perhaps the option has changed?

[donenocode]

Have created a new installation with the same method (HELM (--install=helm option)) using 7.13.0 and this issue still exists.

I have tested the config option 'CHE_LIMITS_USER_WORKSPACES_RUN_COUNT=0' this works as expected and prevents the user from starting workspaces outside of an organization.
I could use this as a short-term work around.

[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.