🚀 KubeSphere 3.1.1 is now available as it extends Kubernetes from the cloud to the edge. Read the introduction for 3.1.x → close
  • English
    • English
    • 简体中文
    1. 1.Experience account: demo1 / Demo123
    2. 2.This account is only allowed to view parts of UI
    3. 3.It's recommended that install KubeSphere in your environment
  •  Star
  1. Documentation / 
  2. Workspace Administration and User Guide / 
  3. Project Quotas

Workspace Administration and User Guide

Last updated:
    Edit

    Project Quotas

    KubeSphere uses Kubernetes requests and limits to control resource (for example, CPU and memory) usage in a project, also known as ResourceQuotas in Kubernetes. Requests make sure a project can get the resources it needs as they are specifically guaranteed and reserved. On the contrary, limits ensure that a project can never use resources above a certain value.

    Besides CPU and memory, you can also set resource quotas for other objects separately such as Pods, Deployments, Jobs, Services and ConfigMaps in a project.

    This tutorial demonstrates how to configure quotas for a project.

    Prerequisites

    You have an available workspace, a project and an account (ws-admin). The account must have the admin role at the workspace level. For more information, see Create Workspaces, Projects, Accounts and Roles.

    Note

    If you use the account project-admin (an account of the admin role at the project level), you can set project quotas as well for a new project (i.e. its quotas remain unset). However, project-admin cannot change project quotas once they are set. Generally, it is the responsibility of ws-admin to set limits and requests for a project. project-admin is responsible for setting limit ranges for containers in a project.

    Set Project Quotas

    1. Log in to the console as ws-admin and go to a project. On the Overview page, you can see project quotas remain unset if the project is newly created. Click Set to configure quotas.

      project-quotas

    2. In the dialog that appears, you can see that KubeSphere does not set any requests or limits for a project by default. To set limits to control CPU and memory resources, use the slider to move to a desired value or enter numbers directly. Leaving a field blank means you do not set any requests or limits.

      set-project-quotas

      Note

      The limit can never be lower than the request.

    3. To set quotas for other resources, click Add Quota Item and select an object from the list.

      set-other-resouce-quotas

    4. Click OK to finish setting quotas.

    5. Go to Basic Information in Project Settings, and you can see all resource quotas for the project.

    6. To change project quotas, click Manage Project on the Basic Information page and select Edit Quota.

      Note

      For a multi-cluster project, the option Edit Quota does not display in the Manage Project drop-down menu. To set quotas for a multi-cluster project, go to Quota Management under Project Settings and click Edit Quota. Note that as a multi-cluster project runs across clusters, you can set resource quotas on different clusters separately.

    7. Change project quotas in the dialog that appears and click OK.

    See Also

    Container Limit Ranges


    Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

    Previous : Workspace Network Isolation
    What’s on this Page