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 an account (). 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 (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, 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. 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.

    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 requests and limits to control CPU and memory resources, use the slider to move to a desired value or input 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.

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

      resrouce-quotas

    5. Change project quotas directly on the Project Quota page and click OK.

    Container Limit Ranges