Merge pull request #51678 from ryan-su-12/sync-main-into-dev-1.34-v2

Merge main branch into dev-1.34

Author: k8s-ci-robot

Makefile

@@ -2,6 +2,9 @@ HUGO_VERSION      = $(shell grep ^HUGO_VERSION netlify.toml | tail -n 1 | cut -d
 NODE_BIN          = node_modules/.bin
 NETLIFY_FUNC      = $(NODE_BIN)/netlify-lambda
 
+# The segments variable is used to specify which segments to render.
+segments          ?= all
+
 # The CONTAINER_ENGINE variable is used for specifying the container engine. By default 'docker' is used
 # but this can be overridden when calling make, e.g.
 # CONTAINER_ENGINE=podman make container-image
@@ -69,7 +72,7 @@ non-production-build: module-check ## Build the non-production site, which adds
 	GOMAXPROCS=1 hugo --cleanDestinationDir --enableGitInfo --environment nonprod
 
 serve: module-check ## Boot the development server.
-	hugo server --buildDrafts --buildFuture --environment development
+	hugo server --buildDrafts --buildFuture --environment development --renderSegments $(segments)
 
 docker-image:
 	@echo -e "$(CCRED)**** The use of docker-image is deprecated. Use container-image instead. ****$(CCEND)"
@@ -118,7 +121,7 @@ container-build: module-check
 container-serve: module-check ## Boot the development server using container.
 	$(CONTAINER_RUN_TTY) --cap-drop=ALL --cap-add=AUDIT_WRITE $(CONTAINER_HUGO_MOUNTS) \
 		-p 1313:1313 $(CONTAINER_IMAGE) \
-		hugo server --buildDrafts --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/public --cleanDestinationDir --noBuildLock
+		hugo server --buildDrafts --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/public --cleanDestinationDir --noBuildLock --renderSegments $(segments)
 
 test-examples:
 	scripts/test_examples.sh install

README.md

@@ -55,10 +55,20 @@ To build the site in a container, run the following:
 
 ```bash
 # You can set $CONTAINER_ENGINE to the name of any Docker-like container tool
+
+# Render the full website
 make container-serve
+
+# Render only a specific language segment (e.g., English)
+make container-serve segments=en
+
+# Render multiple languages (e.g., English and Korean)
+make container-serve segments=en,ko
 ```
 
-If you see errors, it probably means that the hugo container did not have enough computing resources available. To solve it, increase the amount of allowed CPU and memory usage for Docker on your machine ([MacOS](https://docs.docker.com/desktop/settings/mac/) and [Windows](https://docs.docker.com/desktop/settings/windows/)).
+**💡 Tip:** Using _Hugo segments_ speeds up local preview builds, by rendering only selected language(s).
+
+If you see errors, it probably means that the Hugo container did not have enough computing resources available. To solve it, increase the amount of allowed CPU and memory usage for Docker on your machine ([macOS](https://docs.docker.com/desktop/settings/mac/) and [Windows](https://docs.docker.com/desktop/settings/windows/)).
 
 Open up your browser to <http://localhost:1313> to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
 
@@ -70,9 +80,19 @@ To install dependencies, deploy and test the site locally, run:
 
   ```bash
   npm ci
+
+  # Render the full site (default)
   make serve
+
+  # Render only a specific language segment
+  make serve segments=en
+
+  # Render multiple language segments
+  make serve segments=en,ko
   ```
 
+**💡 Tip:** Hugo segments are defined in `hugo.toml` and allow faster rendering by limiting the scope to specific language(s).
+
 - For Windows (PowerShell)
 
   ```powershell
@@ -82,6 +102,7 @@ To install dependencies, deploy and test the site locally, run:
 
 This will start the local Hugo server on port 1313. Open up your browser to <http://localhost:1313> to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
 
+
 ## Building the API reference pages
 
 The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, also known as OpenAPI specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.

content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md

@@ -246,7 +246,7 @@ In order to monitor resources provided by device plugins, monitoring agents need
 discover the set of devices that are in-use on the node and obtain metadata to describe which
 container the metric should be associated with. [Prometheus](https://prometheus.io/) metrics
 exposed by device monitoring agents should follow the
-[Kubernetes Instrumentation Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/instrumentation.md),
+[Kubernetes Instrumentation Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/metric-instrumentation.md),
 identifying containers using `pod`, `namespace`, and `container` prometheus labels.
 
 The kubelet provides a gRPC service to enable discovery of in-use devices, and to provide metadata

content/en/docs/concepts/extend-kubernetes/operator.md

@@ -117,7 +117,7 @@ operator.
 * [Kopf](https://github.com/nolar/kopf) (Kubernetes Operator Pythonic Framework)
 * [kube-rs](https://kube.rs/) (Rust)
 * [kubebuilder](https://book.kubebuilder.io/)
-* [KubeOps](https://buehler.github.io/dotnet-operator-sdk/) (.NET operator SDK)
+* [KubeOps](https://dotnet.github.io/dotnet-operator-sdk/) (.NET operator SDK)
 * [Mast](https://docs.ansi.services/mast/user_guide/operator/)
 * [Metacontroller](https://metacontroller.github.io/metacontroller/intro.html) along with WebHooks that
   you implement yourself

content/en/docs/concepts/services-networking/dns-pod-service.md

@@ -105,7 +105,7 @@ Kube-DNS versions, prior to the implementation of the
 had the following DNS resolution:
 
 ```
-pod-ipv4-address.my-namespace.pod.cluster-domain.example
+<pod-IPv4-address>.<namespace>.pod.<cluster-domain>
 ```
 
 For example, if a Pod in the `default` namespace has the IP address 172.17.0.3,
@@ -121,6 +121,14 @@ Some cluster DNS mechanisms, like [CoreDNS](https://coredns.io/), also provide `
 <pod-ipv4-address>.<service-name>.<my-namespace>.svc.<cluster-domain.example>
 ```
 
+For example, if a Pod in the `cafe` namespace has the IP address 172.17.0.3,
+is an endpoint of a Service named `barista`, and the domain name for your cluster is
+`cluster.local`, then the Pod would have this service-scoped DNS `A` record.
+
+```
+172-17-0-3.barista.cafe.svc.cluster.local
+```
+
 ### Pod's hostname and subdomain fields
 
 Currently when a Pod is created, its hostname (as observed from within the Pod)

content/en/docs/reference/command-line-tools-reference/feature-gates/APIServingWithRoute.md renamed to content/en/docs/reference/command-line-tools-reference/feature-gates/APIServingWithRoutine.md

@@ -1,5 +1,5 @@
 ---
-title: APIServingWithRoute
+title: APIServingWithRoutine
 content_type: feature_gate
 _build:
   list: never

content/en/docs/reference/glossary/kubelet.md

@@ -2,7 +2,7 @@
 title: Kubelet
 id: kubelet
 date: 2018-04-12
-full_link: /docs/reference/generated/kubelet
+full_link: /docs/reference/command-line-tools-reference/kubelet
 short_description: >
   An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.