Merge branch 'stingrayza/workspace-cri-update' into 'master'

Update doc to generalise container runtime

See merge request !122877



Merged-by: Ashraf Khamis <akhamis@gitlab.com>
Approved-by: Ashraf Khamis <akhamis@gitlab.com>
Co-authored-by: Raimund Hook <rhook@gitlab.com>

doc/user/workspace/index.md

@@ -154,6 +154,6 @@ If you already have running workspaces, an administrator must manually delete th
 ## Arbitrary user IDs
 
 You can provide your own container image, which can run as any Linux user ID. It's not possible for GitLab to predict the Linux user ID for a container image.
-GitLab uses the Linux root group ID permission to create, update, or delete files in the container. CRI-O, the container runtime interface used by Kubernetes, has a default group ID of `0` for all containers.
+GitLab uses the Linux root group ID permission to create, update, or delete files in the container. Depending on the container runtime used by the Kubernetes cluster, all containers might have a default group ID of `0`.
 
 If you have a container image that does not support arbitrary user IDs, you cannot create, update, or delete files in a workspace. To create a container image that supports arbitrary user IDs, see the [OpenShift documentation](https://docs.openshift.com/container-platform/4.12/openshift_images/create-images.html#use-uid_create-images).