diff --git a/content/en/docs/components/notebooks/api-reference/notebook-v1.md b/content/en/docs/components/notebooks/api-reference/notebook-v1.md index ce131dd3c2..8a09d32e0c 100644 --- a/content/en/docs/components/notebooks/api-reference/notebook-v1.md +++ b/content/en/docs/components/notebooks/api-reference/notebook-v1.md @@ -33,7 +33,7 @@ Resource Types:
metadata
-
+
Kubernetes meta/v1.ObjectMeta
@@ -118,7 +118,7 @@ string
lastProbeTime
-
+
Kubernetes meta/v1.Time
@@ -232,7 +232,7 @@ int32
containerState
-
+
Kubernetes core/v1.ContainerState
@@ -263,7 +263,7 @@ Kubernetes core/v1.ContainerState
spec
-
+
Kubernetes core/v1.PodSpec
@@ -276,7 +276,7 @@ Kubernetes core/v1.PodSpec
volumes
-
+
[]Kubernetes core/v1.Volume
@@ -291,7 +291,7 @@ More info: https:/
initContainers
-
+
[]Kubernetes core/v1.Container
@@ -316,7 +316,7 @@ More info:
+
[]Kubernetes core/v1.Container
@@ -332,7 +332,7 @@ Cannot be updated.
ephemeralContainers
-
+
[]Kubernetes core/v1.EphemeralContainer
@@ -536,7 +536,7 @@ Optional: Default to false.
securityContext
-
+
Kubernetes core/v1.PodSecurityContext
@@ -551,7 +551,7 @@ Optional: Defaults to empty. See type description for default values of each fi
imagePullSecrets
-
+
[]Kubernetes core/v1.LocalObjectReference
@@ -594,7 +594,7 @@ If not specified, the pod will not have a domainname at all.
affinity
-
+
Kubernetes core/v1.Affinity
@@ -621,7 +621,7 @@ If not specified, the pod will be dispatched by default scheduler.
tolerations
-
+
[]Kubernetes core/v1.Toleration
@@ -635,7 +635,7 @@ If not specified, the pod will be dispatched by default scheduler.
hostAliases
-
+
[]Kubernetes core/v1.HostAlias
@@ -683,7 +683,7 @@ The higher the value, the higher the priority.
dnsConfig
-
+
Kubernetes core/v1.PodDNSConfig
@@ -699,7 +699,7 @@ configuration based on DNSPolicy.
readinessGates
-
+
[]Kubernetes core/v1.PodReadinessGate
@@ -781,7 +781,7 @@ This field is alpha-level as of Kubernetes v1.16, and is only honored by servers
topologySpreadConstraints
-
+
[]Kubernetes core/v1.TopologySpreadConstraint
diff --git a/content/en/docs/components/pipelines/reference/component-spec.md b/content/en/docs/components/pipelines/reference/component-spec.md
index ea0dbf225c..0ed9ded5b5 100644
--- a/content/en/docs/components/pipelines/reference/component-spec.md
+++ b/content/en/docs/components/pipelines/reference/component-spec.md
@@ -91,7 +91,7 @@ This section describes the
* `container`:
Describes the Docker container that implements the component. A portable
subset of the Kubernetes
- [Container v1 spec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.12/#container-v1-core).
+ [Container v1 spec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#container-v1-core).
* `image`: Name of the Docker image.
* `command`: Entrypoint array. The Docker image's
diff --git a/content/en/docs/components/spark-operator/user-guide/writing-sparkapplication.md b/content/en/docs/components/spark-operator/user-guide/writing-sparkapplication.md
index b3749befdb..7d02efd7e3 100644
--- a/content/en/docs/components/spark-operator/user-guide/writing-sparkapplication.md
+++ b/content/en/docs/components/spark-operator/user-guide/writing-sparkapplication.md
@@ -149,7 +149,7 @@ Values specified using those two fields get converted to Spark configuration pro
## Specifying Environment Variables
-There are two fields for specifying environment variables for the driver and/or executor containers, namely `.spec.driver.env` (or `.spec.executor.env` for the executor container) and `.spec.driver.envFrom` (or `.spec.executor.envFrom` for the executor container). Specifically, `.spec.driver.env` (and `.spec.executor.env`) takes a list of [EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#envvar-v1-core), each of which specifies an environment variable or the source of an environment variable, e.g., a name-value pair, a ConfigMap key, a Secret key, etc. Alternatively, `.spec.driver.envFrom` (and `.spec.executor.envFrom`) takes a list of [EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#envfromsource-v1-core) and allows [using all key-value pairs in a ConfigMap or Secret as environment variables](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables). The `SparkApplication` snippet below shows the use of both fields:
+There are two fields for specifying environment variables for the driver and/or executor containers, namely `.spec.driver.env` (or `.spec.executor.env` for the executor container) and `.spec.driver.envFrom` (or `.spec.executor.envFrom` for the executor container). Specifically, `.spec.driver.env` (and `.spec.executor.env`) takes a list of [EnvVar](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#envvar-v1-core), each of which specifies an environment variable or the source of an environment variable, e.g., a name-value pair, a ConfigMap key, a Secret key, etc. Alternatively, `.spec.driver.envFrom` (and `.spec.executor.envFrom`) takes a list of [EnvFromSource](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#envfromsource-v1-core) and allows [using all key-value pairs in a ConfigMap or Secret as environment variables](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables). The `SparkApplication` snippet below shows the use of both fields:
```yaml
spec:
@@ -426,7 +426,7 @@ Note that the mutating admission webhook is needed to use this feature. Please r
## Using Sidecar Containers
-A `SparkApplication` can specify one or more optional sidecar containers for the driver or executor pod, using the optional field `.spec.driver.sidecars` or `.spec.executor.sidecars`. The specification of each sidecar container follows the [Container](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#container-v1-core) API definition. Below is an example:
+A `SparkApplication` can specify one or more optional sidecar containers for the driver or executor pod, using the optional field `.spec.driver.sidecars` or `.spec.executor.sidecars`. The specification of each sidecar container follows the [Container](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#container-v1-core) API definition. Below is an example:
```yaml
spec:
@@ -447,7 +447,7 @@ Note that the mutating admission webhook is needed to use this feature. Please r
## Using Init-Containers
-A `SparkApplication` can optionally specify one or more [init-containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) for the driver or executor pod, using the optional field `.spec.driver.initContainers` or `.spec.executor.initContainers`, respectively. The specification of each init-container follows the [Container](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#container-v1-core) API definition. Below is an example:
+A `SparkApplication` can optionally specify one or more [init-containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) for the driver or executor pod, using the optional field `.spec.driver.initContainers` or `.spec.executor.initContainers`, respectively. The specification of each init-container follows the [Container](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.29/#container-v1-core) API definition. Below is an example:
```yaml
spec: