Latin Abbreviations "vs" Updated to "versus" (#19181)
* grep -lR ' vs ' ./content/en/docs | xargs sed -i '' -e 's/ vs / versus /g' * Update content/en/docs/concepts/configuration/overview.md Co-Authored-By: Tim Bannister <tim@scalefactory.com> * Update content/en/docs/concepts/policy/resource-quotas.md Co-Authored-By: Tim Bannister <tim@scalefactory.com> Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
committed by
vineeth
parent
8e08f65522
commit
0016292e36
@@ -30,7 +30,7 @@ This is a living document. If you think of something that is not on this list bu
|
|||||||
- Put object descriptions in annotations, to allow better introspection.
|
- Put object descriptions in annotations, to allow better introspection.
|
||||||
|
|
||||||
|
|
||||||
## "Naked" Pods vs ReplicaSets, Deployments, and Jobs
|
## "Naked" Pods versus ReplicaSets, Deployments, and Jobs {#naked-pods-vs-replicasets-deployments-and-jobs}
|
||||||
|
|
||||||
- Don't use naked Pods (that is, Pods not bound to a [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) or [Deployment](/docs/concepts/workloads/controllers/deployment/)) if you can avoid it. Naked Pods will not be rescheduled in the event of a node failure.
|
- Don't use naked Pods (that is, Pods not bound to a [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) or [Deployment](/docs/concepts/workloads/controllers/deployment/)) if you can avoid it. Naked Pods will not be rescheduled in the event of a node failure.
|
||||||
|
|
||||||
@@ -108,4 +108,3 @@ The caching semantics of the underlying image provider make even `imagePullPolic
|
|||||||
|
|
||||||
{{% /capture %}}
|
{{% /capture %}}
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -207,7 +207,7 @@ When you create a custom resource, either via a CRDs or an AA, you get many feat
|
|||||||
| Finalizers | Block deletion of extension resources until external cleanup happens. |
|
| Finalizers | Block deletion of extension resources until external cleanup happens. |
|
||||||
| Admission Webhooks | Set default values and validate extension resources during any create/update/delete operation. |
|
| Admission Webhooks | Set default values and validate extension resources during any create/update/delete operation. |
|
||||||
| UI/CLI Display | Kubectl, dashboard can display extension resources. |
|
| UI/CLI Display | Kubectl, dashboard can display extension resources. |
|
||||||
| Unset vs Empty | Clients can distinguish unset fields from zero-valued fields. |
|
| Unset versus Empty | Clients can distinguish unset fields from zero-valued fields. |
|
||||||
| Client Libraries Generation | Kubernetes provides generic client libraries, as well as tools to generate type-specific client libraries. |
|
| Client Libraries Generation | Kubernetes provides generic client libraries, as well as tools to generate type-specific client libraries. |
|
||||||
| Labels and annotations | Common metadata across objects that tools know how to edit for core and custom resources. |
|
| Labels and annotations | Common metadata across objects that tools know how to edit for core and custom resources. |
|
||||||
|
|
||||||
|
|||||||
@@ -379,7 +379,7 @@ pods 0 10
|
|||||||
* `Exist`
|
* `Exist`
|
||||||
* `DoesNotExist`
|
* `DoesNotExist`
|
||||||
|
|
||||||
## Requests vs Limits
|
## Requests compared to Limits {#requests-vs-limits}
|
||||||
|
|
||||||
When allocating compute resources, each container may specify a request and a limit value for either CPU or memory.
|
When allocating compute resources, each container may specify a request and a limit value for either CPU or memory.
|
||||||
The quota can be configured to quota either value.
|
The quota can be configured to quota either value.
|
||||||
|
|||||||
@@ -761,7 +761,7 @@ phase, and therefore is the last admission controller to run.
|
|||||||
`MutatingAdmissionWebhook` appears before it in this list, because it runs
|
`MutatingAdmissionWebhook` appears before it in this list, because it runs
|
||||||
in the mutating phase.
|
in the mutating phase.
|
||||||
|
|
||||||
For earlier versions, there was no concept of validating vs mutating and the
|
For earlier versions, there was no concept of validating versus mutating and the
|
||||||
admission controllers ran in the exact order specified.
|
admission controllers ran in the exact order specified.
|
||||||
|
|
||||||
{{% /capture %}}
|
{{% /capture %}}
|
||||||
|
|||||||
Reference in New Issue
Block a user