API Reference multi-pages for v1.25

Author: feloy

api-ref-assets/api/swagger.json

@@ -4,6 +4,7 @@
     fields:
     - containers
     - initContainers
+    - ephemeralContainers
     - imagePullSecrets
     - enableServiceLinks
     - os
@@ -20,7 +21,9 @@
     - runtimeClassName
     - priorityClassName
     - priority
+    - preemptionPolicy
     - topologySpreadConstraints
+    - overhead
   - name: Lifecycle
     fields:
     - restartPolicy
@@ -48,11 +51,6 @@
   - name: Security context
     fields:
     - securityContext
-  - name: Beta level
-    fields:
-    - ephemeralContainers
-    - preemptionPolicy
-    - overhead
   - name: Deprecated
     fields:
     - serviceAccount
@@ -396,7 +394,7 @@
     - completedIndexes
     - conditions
     - uncountedTerminatedPods
-  - name: Alpha level
+  - name: Beta level
     fields:
     - ready
 
@@ -525,6 +523,7 @@
     - cephfs
     - cinder
     - csi
+    - ephemeral
     - fc
     - flexVolume
     - flocker
@@ -539,9 +538,6 @@
     - scaleIO
     - storageos
     - vsphereVolume
-  - name: Alpha level
-    fields:
-    - ephemeral
   - name: Deprecated
     fields:
     - gitRepo
@@ -591,7 +587,7 @@
     - volumeName
     - storageClassName
     - volumeMode
-  - name: Alpha level
+  - name: Beta level
     fields:
     - dataSource
     - dataSourceRef
@@ -714,6 +710,3 @@
     - resourceVersion
     - selfLink
     - uid
-  - name: Ignored
-    fields:
-    - clusterName

api-ref-assets/config/fields.yaml

@@ -179,9 +179,6 @@ parts:
   - name: PodDisruptionBudget
     group: policy
     version: v1
-  - name: PodSecurityPolicy
-    group: policy
-    version: v1beta1
 - name: Extend Resources
   chapters:
   - name: CustomResourceDefinition

api-ref-assets/config/toc.yaml

@@ -62,7 +62,7 @@ TokenRequestSpec contains client provided parameters of a token request.
 
 - **audiences** ([]string), required
 
-  Audiences are the intendend audiences of the token. A recipient of a token must identitfy themself with an identifier in the list of audiences of the token, and otherwise should reject the token. A token issued for multiple audiences may be used to authenticate against any of the audiences listed but implies a high degree of trust between the target audiences.
+  Audiences are the intendend audiences of the token. A recipient of a token must identify themself with an identifier in the list of audiences of the token, and otherwise should reject the token. A token issued for multiple audiences may be used to authenticate against any of the audiences listed but implies a high degree of trust between the target audiences.
 
 - **boundObjectRef** (BoundObjectReference)
 

content/en/docs/reference/kubernetes-api/authentication-resources/token-request-v1.md

@@ -62,7 +62,7 @@ ClusterRole is a cluster level, logical grouping of PolicyRules that can be refe
 
   - **rules.apiGroups** ([]string)
 
-    APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+    APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. "" represents the core API group and "*" represents all API groups.
 
   - **rules.resources** ([]string)
 

content/en/docs/reference/kubernetes-api/authorization-resources/cluster-role-v1.md

@@ -51,7 +51,7 @@ Role is a namespaced, logical grouping of PolicyRules that can be referenced as
 
   - **rules.apiGroups** ([]string)
 
-    APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.
+    APIGroups is the name of the APIGroup that contains the resources.  If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. "" represents the core API group and "*" represents all API groups.
 
   - **rules.resources** ([]string)
 

content/en/docs/reference/kubernetes-api/authorization-resources/role-v1.md

@@ -356,7 +356,7 @@ NodeStatus is information about the current status of a node.
 
   - **images.names** ([]string)
 
-    Names by which this image is known. e.g. ["registry.k8s.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
+    Names by which this image is known. e.g. ["k8s.gcr.io/hyperkube:v1.0.7", "dockerhub.io/google_containers/hyperkube:v1.0.7"]
 
   - **images.sizeBytes** (int64)
 

content/en/docs/reference/kubernetes-api/cluster-resources/node-v1.md

@@ -70,8 +70,8 @@ PriorityLevelConfigurationSpec specifies the configuration of a priority level.
 
   <a name="LimitedPriorityLevelConfiguration"></a>
   *LimitedPriorityLevelConfiguration specifies how to handle requests that are subject to limits. It addresses two issues:
-   * How are requests for this priority level limited?
-   * What should be done with requests that exceed the limit?*
+    - How are requests for this priority level limited?
+    - What should be done with requests that exceed the limit?*
 
   - **limited.assuredConcurrencyShares** (int32)
 

content/en/docs/reference/kubernetes-api/cluster-resources/priority-level-configuration-v1beta2.md

@@ -188,14 +188,5 @@ ObjectMeta is metadata that all persisted resources must have, which includes al
 
   Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids
 
-### Ignored {#Ignored}
-
-
-- **clusterName** (string)
-
-  Deprecated: ClusterName is a legacy field that was always cleared by the system and never used; it will be removed completely in 1.25.
-  
-  The name in the go struct is changed to help clients detect accidental use.
-
 
 

content/en/docs/reference/kubernetes-api/common-definitions/object-meta.md

@@ -30,27 +30,33 @@ Quantity is a fixed-point representation of a number. It provides convenient mar
 
 The serialization format is:
 
-\<quantity>        ::= \<signedNumber>\<suffix>
-  (Note that \<suffix> may be empty, from the "" case in \<decimalSI>.)
+``` \<quantity>        ::= \<signedNumber>\<suffix>
+
+	(Note that \<suffix> may be empty, from the "" case in \<decimalSI>.)
+
 \<digit>           ::= 0 | 1 | ... | 9 \<digits>          ::= \<digit> | \<digit>\<digits> \<number>          ::= \<digits> | \<digits>.\<digits> | \<digits>. | .\<digits> \<sign>            ::= "+" | "-" \<signedNumber>    ::= \<number> | \<sign>\<number> \<suffix>          ::= \<binarySI> | \<decimalExponent> | \<decimalSI> \<binarySI>        ::= Ki | Mi | Gi | Ti | Pi | Ei
-  (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
+
+	(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
+
 \<decimalSI>       ::= m | "" | k | M | G | T | P | E
-  (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
-\<decimalExponent> ::= "e" \<signedNumber> | "E" \<signedNumber>
+
+	(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
+
+\<decimalExponent> ::= "e" \<signedNumber> | "E" \<signedNumber> ```
 
 No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.
 
 When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.
 
 Before serializing, Quantity will be put in "canonical form". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:
-  a. No precision is lost
-  b. No fractional digits will be emitted
-  c. The exponent (or suffix) is as large as possible.
+
+- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.
+
 The sign will be omitted unless the number is negative.
 
 Examples:
-  1.5 will be serialized as "1500m"
-  1.5Gi will be serialized as "1536Mi"
+
+- 1.5 will be serialized as "1500m" - 1.5Gi will be serialized as "1536Mi"
 
 Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.