![]() Automatic merge from submit-queue Add support for kubectl create quota command Follow-up of https://github.com/kubernetes/kubernetes/pull/19625 ``` Create a resourcequota with the specified name, hard limits and optional scopes Usage: kubectl create quota NAME [--hard=key1=value1,key2=value2] [--scopes=Scope1,Scope2] [--dry-run=bool] [flags] Aliases: quota, q Examples: // Create a new resourcequota named my-quota $ kubectl create quota my-quota --hard=cpu=1,memory=1G,pods=2,services=3,replicationcontrollers=2,resourcequotas=1,secrets=5,persistentvolumeclaims=10 // Create a new resourcequota named best-effort $ kubectl create quota best-effort --hard=pods=100 --scopes=BestEffort ``` |
||
---|---|---|
.. | ||
admin | ||
api-reference | ||
design | ||
devel | ||
getting-started-guides | ||
images | ||
man/man1 | ||
proposals | ||
user-guide | ||
yaml/kubectl | ||
OWNERS | ||
README.md | ||
api.md | ||
reporting-security-issues.md | ||
roadmap.md | ||
troubleshooting.md | ||
warning.png | ||
whatisk8s.md |
README.md
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.3/docs/README.md).Documentation for other releases can be found at releases.k8s.io.
Kubernetes Documentation: releases.k8s.io/HEAD
-
The User's guide is for anyone who wants to run programs and services on an existing Kubernetes cluster.
-
The Cluster Admin's guide is for anyone setting up a Kubernetes cluster or administering it.
-
The Developer guide is for anyone wanting to write programs that access the Kubernetes API, write plugins or extensions, or modify the core code of Kubernetes.
-
The Kubectl Command Line Interface is a detailed reference on the
kubectl
CLI. -
The API object documentation is a detailed description of all fields found in core API objects.
-
An overview of the Design of Kubernetes
-
There are example files and walkthroughs in the examples folder.
-
If something went wrong, see the troubleshooting document for how to debug. You should also check the known issues for the release you're using.
-
To report a security issue, see Reporting a Security Issue.