Kubernetes Tenant/Project Quotas

When you are creating or editing a Kubernetes tenant (see Creating a New Kubernetes Tenant or Editing an Existing Kubernetes Tenant), selecting the Quotas tab allows you to adjust CPU, storage, and QOS quotas for optimal Kubernetes tenant performance.



This tab allows you to specify the following settings:

  • Maximum Cores: Enter the maximum number of virtual CPU cores that should be made available for use by this Kubernetes tenant.

    By default, this field will display a value equal to 25% of the available CPU cores with the appropriate license type, but you can specify any number you want. If you are creating or editing a Kubernetes tenant, then you may leave this field blank if you do not want to specify a quota.See Virtual Cores, RAM, Storage, and GPU Devices for important information about how virtual CPU cores are used. See also Licensing and License Tab for information on adding/updating a license.

  • Maximum Memory (GB): Enter the maximum amount of RAM in GB that HPE Ezmeral Runtime Enterprise should make available for use by this Kubernetes tenant.

    By default, this field will display a value equal to 25% of the available memory that is not reserved for HPE Ezmeral Runtime Enterprise services, but you can specify any number you want, or leave this field blank if you do not want to specify a quota. Please see Virtual Cores, RAM, Storage, and GPU Devices for important information about how memory is used. See also Licensing and License Tab for information on adding/updating a license.

  • Maximum Ephemeral Storage (GB): Enter the maximum space the tenant may use for ephemeral storage, in GB.

    By default, this field will display a value equal to 25% of the available ephemeral storage, but you can specify any number you want, or leave this field blank if you do not want to specify a quota. See Node Storage for more information about ephemeral storage.

  • GPU Devices: Enter the maximum number of GPU devices the Kubernetes tenant may use.

    By default, this field will display a value of 0, but you can specify any number you want, or leave this field blank if you do not want to specify a quota. See Virtual Cores, RAM, Storage, and GPU Devices for more information about how GPU devices are used.

  • Maximum Tenant Storage (GB): If the Kubernetes tenant uses local HDFS for tenant storage, then you can specify the maximum space to use for this storage, in GB.

    By default, this field will display a value equal to 25% of the available tenant storage, but you can specify any number you want, or leave this field blank if you do not want to specify a quota. See Tenant and Project Storage for more information about tenant storage.

NOTE A Kubernetes tenant that performs lots of I/O to the base HDFS can exceed its assigned quota. This error appears as an INFO item in the NameNode log on the Controller host. Further, the CNODE log reports a socket disconnect (which can have multiple causes).

When diagnosing an I/O failure between a virtual node and the base HDFS, be sure to look for is the character string quota exceeded in the NameNode log.

When you have finished specifying quota settings, continue creating or editing the Kubernetes tenant, as described in Creating a New Kubernetes Tenant or Editing an Existing Kubernetes Tenant, as appropriate.