Fix typos
parent
cd897207ec
commit
1213635880
|
@ -438,7 +438,7 @@ If you want to use project quotas, you should:
|
|||
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
|
||||
in the kubelet configuration.
|
||||
|
||||
* Ensure that the the root filesystem (or optional runtime filesystem)
|
||||
* Ensure that the root filesystem (or optional runtime filesystem)
|
||||
has project quotas enabled. All XFS filesystems support project quotas.
|
||||
For ext4 filesystems, you need to enable the project quota tracking feature
|
||||
while the filesystem is not mounted.
|
||||
|
|
|
@ -1193,7 +1193,7 @@ the [legacy ABAC policy](/docs/reference/access-authn-authz/abac/#policy-file-fo
|
|||
```
|
||||
|
||||
To explain that first command line option in detail: if earlier authorizers, such as Node,
|
||||
deny a request, then the the RBAC authorizer attempts to authorize the API request. If RBAC
|
||||
deny a request, then the RBAC authorizer attempts to authorize the API request. If RBAC
|
||||
also denies that API request, the ABAC authorizer is then run. This means that any request
|
||||
allowed by *either* the RBAC or ABAC policies is allowed.
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ The `healthz` endpoint is deprecated (since Kubernetes v1.16), and you should us
|
|||
The `livez` endpoint can be used with the `--livez-grace-period` [flag](/docs/reference/command-line-tools-reference/kube-apiserver) to specify the startup duration.
|
||||
For a graceful shutdown you can specify the `--shutdown-delay-duration` [flag](/docs/reference/command-line-tools-reference/kube-apiserver) with the `/readyz` endpoint.
|
||||
Machines that check the `health`/`livez`/`readyz` of the API server should rely on the HTTP status code.
|
||||
A status code `200` indicates the the API server is `healthy`/`live`/`ready`, depending of the called endpoint.
|
||||
A status code `200` indicates the API server is `healthy`/`live`/`ready`, depending of the called endpoint.
|
||||
The more verbose options shown below are intended to be used by human operators to debug their cluster or specially the state of the API server.
|
||||
|
||||
The following examples will show how you can interact with the health API endpoints.
|
||||
|
|
|
@ -153,7 +153,7 @@ An older kubectl plugin mechanism provided environment variables such as `KUBECT
|
|||
kubectl plugins must parse and validate all of the arguments passed to them.
|
||||
See [using the command line runtime package](#using-the-command-line-runtime-package) for details of a Go library aimed at plugin authors.
|
||||
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
|
||||
If you run `kubectl foo bar baz arg1 --flag=value arg2`, kubectl's plugin mechanism will first try to find the plugin with the longest possible name, which in this case
|
||||
would be `kubectl-foo-bar-baz-arg1`. Upon not finding that plugin, kubectl then treats the last dash-separated value as an argument (`arg1` in this case), and attempts to find the next longest possible name, `kubectl-foo-bar-baz`.
|
||||
|
|
|
@ -1158,7 +1158,7 @@ the [legacy ABAC policy](/docs/reference/access-authn-authz/abac/#policy-file-fo
|
|||
```
|
||||
|
||||
To explain that first command line option in detail: if earlier authorizers, such as Node,
|
||||
deny a request, then the the RBAC authorizer attempts to authorize the API request. If RBAC
|
||||
deny a request, then the RBAC authorizer attempts to authorize the API request. If RBAC
|
||||
also denies that API request, the ABAC authorizer is then run. This means that any request
|
||||
allowed by *either* the RBAC or ABAC policies is allowed.
|
||||
|
||||
|
|
|
@ -815,7 +815,7 @@ If you want to use project quotas, you should:
|
|||
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
|
||||
in the kubelet configuration.
|
||||
|
||||
* Ensure that the the root filesystem (or optional runtime filesystem)
|
||||
* Ensure that the root filesystem (or optional runtime filesystem)
|
||||
has project quotas enabled. All XFS filesystems support project quotas.
|
||||
For ext4 filesystems, you need to enable the project quota tracking feature
|
||||
while the filesystem is not mounted.
|
||||
|
|
|
@ -243,14 +243,14 @@ An older kubectl plugin mechanism provided environment variables such as `KUBECT
|
|||
kubectl plugins must parse and validate all of the arguments passed to them.
|
||||
See [using the command line runtime package](#using-the-command-line-runtime-package) for details of a Go library aimed at plugin authors.
|
||||
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
-->
|
||||
kubeclt 插件必须解析并检查传递给它们的所有参数。
|
||||
参阅[使用命令行运行时包](#using-the-command-line-runtime-package)了解针对
|
||||
插件开发人员的 Go 库的细节。
|
||||
|
||||
<!--
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
Here are some additional cases where users invoke your plugin while providing additional flags and arguments. This builds upon the `kubectl-foo-bar-baz` plugin from the scenario above.
|
||||
-->
|
||||
这里是一些用户调用你的插件的时候提供额外标志和参数的场景。
|
||||
这些场景时基于上述案例中的 `kubectl-foo-bar-baz` 插件的。
|
||||
|
|
Loading…
Reference in New Issue