Merge remote-tracking branch 'upstream/main' into merged-main-dev-1.30

Author: drewhagen

OWNERS_ALIASES

@@ -2,19 +2,16 @@ aliases:
   sig-docs-blog-owners: # Approvers for blog content
     - mrbobbytables
     - nate-double-u
-    - onlydole
     - sftim
   sig-docs-blog-reviewers: # Reviewers for blog content
     - Gauravpadam
     - mrbobbytables
     - nate-double-u
-    - onlydole
     - sftim
   sig-docs-localization-owners: # Admins for localization content
     - a-mccarthy
     - divya-mohan0209
     - natalisucks
-    - onlydole
     - reylejano
     - sftim
     - seokho-son
@@ -32,7 +29,6 @@ aliases:
     - katcosgrove # RT 1.30 Lead
     - natalisucks
     - nate-double-u
-    - onlydole
     - reylejano
     - sftim
     - tengqm
@@ -45,7 +41,6 @@ aliases:
     - mengjiao-liu
     - natalisucks
     - nate-double-u
-    - onlydole
     - reylejano
     - sftim
     - shannonxtreme
@@ -126,7 +121,6 @@ aliases:
   sig-docs-leads: # Website chairs and tech leads
     - divya-mohan0209
     - natalisucks
-    - onlydole
     - reylejano
     - sftim
     - tengqm
@@ -231,7 +225,7 @@ aliases:
     - jimangel # Release Manager Associate
     - jrsapi # Release Manager Associate
     - salaxander # Release Manager Associate
-# authoritative source: https://github.com/kubernetes/committee-security-response/blob/main/OWNERS_ALIASES
+  # authoritative source: https://github.com/kubernetes/committee-security-response/blob/main/OWNERS_ALIASES
   committee-security-response:
     - cjcullen
     - cji
@@ -241,7 +235,7 @@ aliases:
     - ritazh
     - SaranBalaji90
     - tabbysable
-# authoritative source: https://github.com/kubernetes/sig-security/blob/main/OWNERS_ALIASES
+  # authoritative source: https://github.com/kubernetes/sig-security/blob/main/OWNERS_ALIASES
   sig-security-leads:
     - IanColdwater
     - tabbysable

assets/scss/_custom.scss

@@ -680,6 +680,11 @@ main.content {
   }
 }
 
+.td-blog .header-hero h1, .td-blog .header-hero h2 {
+  font-size: 2.25rem; // match rest of site, even if it is actually h2
+  margin-bottom: 20px;
+}
+
 /* CASE-STUDIES */
 
 // Many of the case studies have small variations in markup and styles;
@@ -819,7 +824,8 @@ body.td-documentation {
   }
 }
 
-#announcement + .header-hero.filler {
+/* don't display the hero header for some pages when there is a banner active */
+#announcement + .header-hero.filler, .td-page.td-blog #announcement + .header-hero {
   display: none;
 }
 

content/en/docs/concepts/extend-kubernetes/api-extension/_index.md

@@ -2,3 +2,18 @@
 title: Extending the Kubernetes API
 weight: 30
 ---
+
+Custom resources are extensions of the Kubernetes API. Kubernetes provides two ways to add custom resources to your cluster:
+
+- The [CustomResourceDefinition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
+  (CRD) mechanism allows you to declaratively define a new custom API with an API group, kind, and
+  schema that you specify.
+  The Kubernetes control plane serves and handles the storage of your custom resource. CRDs allow you to
+  create new types of resources for your cluster without writing and running a custom API server. 
+- The [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/)
+  sits behind the primary API server, which acts as a proxy.
+  This arrangement is called API Aggregation (AA), which allows you to provide
+  specialized implementations for your custom resources by writing and
+  deploying your own API server.
+  The main API server delegates requests to your API server for the custom APIs that you specify,
+  making them available to all of its clients.

content/en/docs/reference/command-line-tools-reference/feature-gates/stateful-set-auto-delete-pvc.md

@@ -12,7 +12,7 @@ stages:
     fromVersion: "1.23"
     toVersion: "1.26"
   - stage: beta
-    defaultValue: false
+    defaultValue: true
     fromVersion: "1.27"
 ---
 Allows the use of the optional `.spec.persistentVolumeClaimRetentionPolicy` field, 

content/en/docs/tasks/manage-gpus/scheduling-gpus.md

@@ -64,7 +64,7 @@ spec:
           gpu-vendor.example/example-gpu: 1 # requesting 1 GPU
 ```
 
-## Clusters containing different types of GPUs
+## Manage clusters with different types of GPUs
 
 If different nodes in your cluster have different types of GPUs, then you
 can use [Node Labels and Node Selectors](/docs/tasks/configure-pod-container/assign-pods-nodes/)
@@ -83,10 +83,46 @@ a different label key if you prefer.
 
 ## Automatic node labelling {#node-labeller}
 
-If you're using AMD GPU devices, you can deploy
-[Node Labeller](https://github.com/RadeonOpenCompute/k8s-device-plugin/tree/master/cmd/k8s-node-labeller).
-Node Labeller is a {{< glossary_tooltip text="controller" term_id="controller" >}} that automatically
-labels your nodes with GPU device properties.
+As an administrator, you can automatically discover and label all your GPU enabled nodes
+by deploying Kubernetes [Node Feature Discovery](https://github.com/kubernetes-sigs/node-feature-discovery) (NFD).
+NFD detects the hardware features that are available on each node in a Kubernetes cluster.
+Typically, NFD is configured to advertise those features as node labels, but NFD can also add extended resources, annotations, and node taints.
+NFD is compatible with all [supported versions](/releases/version-skew-policy/#supported-versions) of Kubernetes.
+By default NFD create the [feature labels](https://kubernetes-sigs.github.io/node-feature-discovery/master/usage/features.html) for the detected features.
+Administrators can leverage NFD to also taint nodes with specific features, so that only pods that request those features can be scheduled on those nodes.
 
-Similar functionality for NVIDIA is provided by
-[GPU feature discovery](https://github.com/NVIDIA/gpu-feature-discovery/blob/main/README.md).
+You also need a plugin for NFD that adds appropriate labels to your nodes; these might be generic
+labels or they could be vendor specific. Your GPU vendor may provide a third party
+plugin for NFD; check their documentation for more details.
+
+{{< highlight yaml "linenos=false,hl_lines=6-18" >}}
+apiVersion: v1
+kind: Pod
+metadata:
+  name: example-vector-add
+spec:
+  # You can use Kubernetes node affinity to schedule this Pod onto a node
+  # that provides the kind of GPU that its container needs in order to work
+  affinity:
+    nodeAffinity:
+      requiredDuringSchedulingIgnoredDuringExecution:
+        nodeSelectorTerms:
+        - matchExpressions:
+          - key: "gpu.gpu-vendor.example/installed-memory"
+            operator: Gt # (greater than)
+            values: ["40535"]
+          - key: "feature.node.kubernetes.io/pci-10.present" # NFD Feature label
+            values: ["true"] # (optional) only schedule on nodes with PCI device 10
+  restartPolicy: OnFailure
+  containers:
+    - name: example-vector-add
+      image: "registry.example/example-vector-add:v42"
+      resources:
+        limits:
+          gpu-vendor.example/example-gpu: 1 # requesting 1 GPU
+{{< /highlight >}}
+
+#### GPU vendor implementations
+
+- [Intel](https://intel.github.io/intel-device-plugins-for-kubernetes/cmd/gpu_plugin/README.html)
+- [NVIDIA](https://github.com/NVIDIA/gpu-feature-discovery/#readme)

content/id/docs/tasks/configure-pod-container/configure-service-account.md

@@ -174,7 +174,7 @@ Isi dari `token` tidak dirinci di sini.
 - Membuat sebuah imagePullSecret, seperti yang dijelaskan pada [Menentukan ImagePullSecret pada Pod](/id/docs/concepts/containers/images/#tentukan-imagepullsecrets-pada-sebuah-pod).
 
     ```shell
-    kubectl create secret docker-registry myregistrykey --docker-server=DUMMY_SERVER \
+    kubectl create secret docker-registry myregistrykey --docker-server=<registry name> \
             --docker-username=DUMMY_USERNAME --docker-password=DUMMY_DOCKER_PASSWORD \
             --docker-email=DUMMY_DOCKER_EMAIL
     ```
@@ -250,7 +250,7 @@ kubectl replace serviceaccount default -f ./sa.yaml
 Ketika Pod baru dibuat dalam Namespace yang sedang aktif dan menggunakan ServiceAccount, Pod baru akan memiliki _field_ `spec.imagePullSecrets` yang ditentukan secara otomatis:
 
 ```shell
-kubectl run nginx --image=nginx --restart=Never
+kubectl run nginx --image=<registry name>/nginx --restart=Never
 kubectl get pod nginx -o=jsonpath='{.spec.imagePullSecrets[0].name}{"\n"}'
 ```
 

content/ru/examples/application/guestbook/frontend-deployment.yaml

@@ -17,7 +17,7 @@ spec:
     spec:
       containers:
       - name: php-redis
-        image: gcr.io/google_samples/gb-frontend:v5
+        image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5
         env:
         - name: GET_HOSTS_FROM
           value: "dns"

content/ru/examples/application/guestbook/redis-follower-deployment.yaml

@@ -21,7 +21,7 @@ spec:
     spec:
       containers:
       - name: follower
-        image: gcr.io/google_samples/gb-redis-follower:v2
+        image: us-docker.pkg.dev/google-samples/containers/gke/gb-redis-follower:v2
         resources:
           requests:
             cpu: 100m