Merge pull request #99005 from jab-rh/apis-4-20-0rc0

Add 4.20.0 rc0 APIs

Author: jab-rh

rest_api/autoscale_apis/clusterautoscaler-autoscaling-openshift-io-v1.adoc

@@ -129,6 +129,10 @@ More info: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscal
 | `object`
 | Configuration of scale down operation
 
+| `scaleUp`
+| `object`
+| Configuration of scale up operation
+
 | `skipNodesWithLocalStorage`
 | `boolean`
 | Enables/Disables `--skip-nodes-with-local-storage` CA feature flag. If true cluster autoscaler will never delete nodes with pods with local storage, e.g. EmptyDir or HostPath. true by default at autoscaler
@@ -331,6 +335,28 @@ Required::
 | `string`
 | Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down
 
+|===
+=== .spec.scaleUp
+Description::
++
+--
+Configuration of scale up operation
+--
+
+Type::
+  `object`
+
+
+
+
+[cols="1,1,1",options="header"]
+|===
+| Property | Type | Description
+
+| `newPodScaleUpDelay`
+| `string`
+| Scale up delay for new pods, if omitted defaults to 0 seconds
+
 |===
 === .status
 Description::

rest_api/machine_apis/containerruntimeconfig-machineconfiguration-openshift-io-v1.adoc

@@ -98,7 +98,12 @@ Type::
 
 | `defaultRuntime`
 | `string`
-| defaultRuntime is the name of the OCI runtime to be used as the default.
+| defaultRuntime is the name of the OCI runtime to be used as the default for containers.
+Allowed values are `runc` and `crun`.
+When set to `runc`, OpenShift will use runc to execute the container
+When set to `crun`, OpenShift will use crun to execute the container
+When omitted, this means no opinion and the platform is left to choose a reasonable default,
+which is subject to change over time. Currently, the default is `crun`.
 
 | `logLevel`
 | `string`

rest_api/monitoring_apis/alertmanager-monitoring-coreos-com-v1.adoc

@@ -233,6 +233,15 @@ Use case is e.g. spanning an Alertmanager cluster across Kubernetes clusters wit
 | HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the
 pod's hosts file.
 
+| `hostUsers`
+| `boolean`
+| HostUsers supports the user space in Kubernetes.
+
+More info: https://kubernetes.io/docs/tasks/configure-pod-container/user-namespaces/
+
+The feature requires at least Kubernetes 1.28 with the `UserNamespacesSupport` feature gate enabled.
+Starting Kubernetes 1.33, the feature is enabled by default.
+
 | `image`
 | `string`
 | Image if specified has precedence over baseImage, tag and sha
@@ -294,8 +303,8 @@ UI, not the gossip communication.
 | `integer`
 | Minimum number of seconds for which a newly created pod should be ready
 without any of its container crashing for it to be considered available.
-Defaults to 0 (pod will be considered available as soon as it is ready)
-This is an alpha field from kubernetes 1.22 until 1.24 which requires enabling the StatefulSetMinReadySeconds feature gate.
+
+If unset, pods will be considered available as soon as they are ready.
 
 | `nodeSelector`
 | `object (string)`
@@ -304,7 +313,7 @@ This is an alpha field from kubernetes 1.22 until 1.24 which requires enabling t
 | `paused`
 | `boolean`
 | If set to true all actions on the underlying managed objects are not
-goint to be performed, except for delete actions.
+going to be performed, except for delete actions.
 
 | `persistentVolumeClaimRetentionPolicy`
 | `object`