Warning
This page was translated from the original Japanese version by PLaMo Translate. The Japanese version is authoritative; the English translation may contain inaccuracies.
Monitoring Organizational Resource Usage
PFCP implements quotas at the organizational level rather than per Namespace, applying a limit to the total resource usage across all Namespaces within an organization. Attempting to create resources beyond this limit will result in creation failures.
You can check both the total used resources and the usage limits from your organization’s Resource Quota page in the portal.
Note
If you need to request quota relaxation, please contact our support team.
Checking Resource Quotas
To manage resource quotas across organizational Namespaces collectively, PFCP utilizes the Hierarchical Resource Quota feature. You can view the hierarchical resource quota limits and usage status through the following methods:
Checking Resource Quotas via the Grafana Dashboard
PFCP provides a Grafana dashboard for monitoring hierarchical resource quotas. In the Grafana dashboard here, navigate to “PFCP > HNC / HRQ / Tenant Resource Hard Limit & Usage” to view your organization-wide resource quotas.
Checking Resource Quotas Using Command Line Tools
By installing the kubectl-hns plugin, you can check resource quotas from your terminal.
The following command allows you to view your organization’s total resource usage status:
$ kubectl get hrq -o yaml -n org-<organization-name>
The output will include two key fields: .status.hard and .status.used.
.status.hard: Indicates the maximum number of resources that can be created under the specified Namespace. You cannot create more resources than this limit..status.used: Shows the total count of resources that have already been created under the specified Namespace.
$ kubectl get hrq org-resource-quota -o yaml -n org-<org-name>
apiVersion: hnc.x-k8s.io/v1alpha2
kind: HierarchicalResourceQuota
metadata:
name: org-resource-quota
namespace: org-<org-name>
spec:
hard:
count/configmaps: "100"
count/cronjobs.batch: "100"
...
status:
hard:
count/configmaps: "100"
count/cronjobs.batch: "100"
...
used:
count/configmaps: "3"
count/cronjobs.batch: "0"
...