Project Quotas

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

    This tutorial demonstrates how to configure quotas for a project.

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

    Note

    If you use the user (a user 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, cannot change project quotas once they are set. Generally, it is the responsibility of ws-admin to set limits and requests for a project. is responsible for for containers in a project.

    1. In the displayed dialog box, 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.

      Note

      The limit can never be lower than the request.

    2. Click OK to finish setting quotas.

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

    Container Limit Ranges