Eclipse Che logo Eclipse Che Documentation
Home Blog Source Code

Documentation

  • Discover
    • What is Che?
    • Architecture overview
      • Server components
        • Che operator
        • DevWorkspace operator
        • Gateway
        • User dashboard
        • Che server
        • Devfile registry
        • Plugin registry
      • User workspaces
    • Supported platforms
    • Common user roles and tasks
  • Install
    • Che installation overview
    • Requirements
      • Supported platforms
      • Calculate Che resource requirements
      • Che scalability
      • Install the chectl management tool
    • Install Che
      • Deploy on OpenShift
        • Install Che on OpenShift using CLI
        • Install Che on OpenShift using the web console
        • Install Che on OpenShift with Keycloak as external identity provider
      • Deploy on Kubernetes
        • Install Che on Microsoft Azure
        • Install Che on Amazon Elastic Kubernetes Service
        • Install Che on the virtual Kubernetes cluster
      • Deploy locally
        • Install Che on Red Hat OpenShift Local
        • Install Che on Minikube
        • Install Che on Minikube with Keycloak as the OIDC provider
      • Deploy in a restricted environment
        • Install Che in a restricted environment
      • Using chectl to configure the CheCluster Custom Resource during installation
      • Find the FQDN
      • Permissions
        • Permissions for CLI installation
        • Permissions for web console installation
    • Verify the Che installation
    • Next steps after installation
    • Uninstall Che
  • User Guide
    • Getting started with Che
      • Starting a workspace from a Git repository URL
        • Optional parameters for the URLs for starting a new workspace
          • URL parameter concatenation
          • URL parameter for the IDE
          • URL parameter for the IDE image
          • URL parameter for starting duplicate workspaces
          • URL parameter for the devfile file name
          • URL parameter for the devfile file path
          • URL parameter for the workspace storage
          • URL parameter for additional remotes
          • URL parameter for a container image
          • URL parameter for a memory limit
          • URL parameter for a CPU limit
          • URL parameter for the existing workspace name
          • URL parameter for the AI provider
      • Starting a workspace from a raw devfile URL
      • Basic actions you can perform on a workspace
      • Restoring workspaces from backups
        • Restoring a workspace from a backup
        • Viewing backups in the dashboard
      • Authenticating to a Git server from a workspace
      • Using the fuse-overlayfs storage driver for Podman and Buildah
        • Accessing /dev/fuse
        • Enabling fuse-overlayfs with a ConfigMap
      • Running containers with kubedock
      • Prevent workspace idling for long-running commands
    • Using Che in team workflow
      • Badge for first-time contributors
      • Reviewing pull and merge requests
      • Try in Web IDE GitHub action
    • Customizing workspace components
    • Introduction to devfile in Che
    • IDEs in workspaces
      • Microsoft Visual Studio Code - Open Source
      • Connecting Visual Studio Code to a Che workspace
      • Defining a common IDE
    • Using AI assistants in workspaces
      • Configuring an AI provider API key
      • Changing the AI tool on a workspace
    • Using credentials and configurations in workspaces
      • Mounting Secrets
        • Creating image pull Secrets
        • Using a Git-provider access token
      • Mounting ConfigMaps
        • Mounting Git configuration
        • Mounting SSH configuration
      • Enabling artifact repositories in a restricted environment
        • Maven
        • Gradle
        • npm
        • Python
        • Go
        • NuGet
    • Requesting persistent storage for workspaces
    • Integrating with Kubernetes
      • Managing workspaces with Kubernetes APIs
      • Automatic Kubernetes token injection
      • Navigating Che from OpenShift Developer Perspective
      • Navigating OpenShift web console from Che
    • Troubleshooting Che
      • Viewing Che workspaces logs
        • Workspace logs in CLI
        • Workspace logs in OpenShift console
        • Language servers and debug adapters logs in the editor
      • Debugging a workspace
      • Troubleshooting slow workspaces
      • Troubleshooting network problems
      • Troubleshooting webview loading error
  • Upgrade
    • Upgrade Che
      • Choose how updates are applied
      • Approve a pending upgrade in the web console
      • Upgrade Che from the command line
      • Upgrade in an air-gapped environment
      • Update the chectl management tool
      • Fix a duplicate DevWorkspace Operator after a cluster upgrade
  • Secure
    • Protect your deployment
    • Control who can access Che
      • Grant additional permissions to users
      • Restrict access to specific users and groups
      • Remove user data for GDPR compliance
  • Optimize performance
    • Caching images for faster workspace start
      • Installing Kubernetes Image Puller
        • Installing the Kubernetes Image Puller operator on Kubernetes cluster by using CLI
        • Installing Image Puller on OpenShift using CLI
        • Installing Image Puller on OpenShift by using the web console
      • Configuring Kubernetes Image Puller
        • Configuring Image Puller to pre-pull default Che images
        • Configuring Image Puller to pre-pull custom images
        • Configuring Image Puller to pre-pull additional images
      • Retrieving the default list of images for Kubernetes Image Puller
    • Configuring autoscaling
      • Configuring number of replicas for a Eclipse Che container
      • Configuring machine autoscaling
  • Configure
    • Configure the platform
      • Customize the central configuration
        • How the central configuration works
        • Edit the central configuration from the command line
        • CheCluster Custom Resource fields reference
      • Inject configuration into server components
        • Inject files from Secrets and ConfigMaps into containers
        • Fine-tune the Che server
      • Customize the developer dashboard
        • Customize the dashboard samples for your team
        • Apply your organization’s branding to the dashboard
      • Use the Che server API
    • Configure workspaces
      • Organize workspace namespaces
        • How workspace namespaces are organized
        • Set the workspace namespace naming convention
        • Provision projects in advance
        • Synchronize resources across user namespaces
        • Use Kubernetes namespaces instead of Kubernetes projects
      • Set workspace policies for all users
        • Limit the number of workspaces that a user can keep
        • Limit the number of workspaces that all users can run simultaneously
        • Enable users to run multiple workspaces simultaneously
        • Trust self-signed Git server certificates
        • Control which nodes run workspaces
        • Restrict which URLs can create workspaces
        • Enable container run capabilities
    • Configure networking and storage
      • Set up network access for workspaces
        • Restrict network traffic between workspaces
        • Use a custom hostname for the dashboard
        • Deploy with a self-signed TLS certificate
        • Trust custom TLS certificates for external services
        • Add labels and annotations to workspace routes
        • Set a custom domain for workspace URLs
        • Route traffic through a proxy
      • Control where workspace data is stored
        • Use a custom storage provisioner
        • Choose how workspace data is persisted
        • Adjust workspace storage capacity
        • How workspace files persist across restarts
      • Enable fuse-overlayfs for container builds
        • When to enable fuse-overlayfs
        • Enable access to /dev/fuse for Kubernetes versions older than 4.15
        • Enable fuse-overlayfs for all workspaces
      • Back up workspaces
        • Back up workspaces
        • Configure backup with the integrated Kubernetes registry
        • Configure backup with a regular OCI-compatible registry
  • Administration Guide
    • Configuring observability
      • The Woopra telemetry plugin
      • Creating a telemetry plugin
      • Configuring server logging
      • Collecting logs using chectl
      • Monitoring the DevWorkspace Operator
      • Monitoring Che Server
    • Configuring OAuth for Git providers
      • Configuring OAuth 2.0 for GitHub
      • Configuring OAuth 2.0 for GitLab
      • Configuring OAuth 2.0 for a Bitbucket Server
      • Configuring OAuth 2.0 for the Bitbucket Cloud
      • Configuring OAuth 1.0 for a Bitbucket Server
      • Configuring OAuth 2.0 for Microsoft Azure DevOps Services
    • Managing IDE extensions
      • Extensions for Microsoft Visual Studio Code - Open Source
      • Configure the Open VSX registry URL
      • Deploy Open VSX from source
      • Deploy Open VSX from a workspace
      • Configure internal Open VSX access
      • Delete an extension using the Open VSX API
      • Delete an extension from the PostgreSQL database
    • Configuring Visual Studio Code - Open Source ("Code - OSS")
      • Configuring single and multiroot workspaces
      • Configure trusted extensions for Microsoft Visual Studio Code
      • Configure default extensions
      • Manage extension installation with ConfigMap
      • Applying editor configurations
    • Configuring editors definitions
      • Show deprecated editors
      • Configuring default editor
      • Concealing editors
      • Configuring editors download urls
      • Configuring AI providers
        • AI provider API key secret reference
    • Extensions
      • OpenShift Connector
        • Features of OpenShift Connector
        • Installing OpenShift Connector in Eclipse Che
        • Authenticating with OpenShift Connector from Eclipse Che
        • Creating Components with OpenShift Connector in Eclipse Che
        • Connecting source code from GitHub to a OpenShift Component
    • Che glossary
Documentation next
  • Documentation
    • next
  • Documentation
  • Configure
  • Configure workspaces
  • Organize workspace namespaces
  • How workspace namespaces are organized
Edit this Page

How workspace namespaces are organized

For each user, Che isolates workspaces in a namespace. Che identifies the user namespace by the presence of labels and annotations. When starting a workspace, if the required namespace doesn’t exist, Che creates the namespace using a template name.

Platform administrators can modify Che behavior by:

  • Set the workspace namespace naming convention

  • Provision projects in advance

  • Synchronize resources across user namespaces

Eclipse Foundation | Privacy Policy | Terms of Use | Eclipse Public License | Legal Resources