Fix broken links from "overview/components/#..." to "architecture/#..." (#47724)

* replace "docs/concepts/overview/components/#" with "docs/concepts/architecture/#" in "content/en/**/*.*"

* revert changes in old blog posts

content/en/blog/_posts/2023-08-31-legacy-package-repository-deprecation/index.md

@@ -51,7 +51,7 @@ generally using their own Kubernetes distributions and therefore they don't use
 packages provided by the Kubernetes project; more importantly, if someone else is
 managing Kubernetes for you, then they would usually take responsibility for that check.
 
-If you have a managed [control plane](/docs/concepts/overview/components/#control-plane-components)
+If you have a managed [control plane](/docs/concepts/architecture/#control-plane-components)
 but you are responsible for **managing the nodes yourself**, and any of those nodes run Linux,
 you should [check](#check-if-affected) whether you are affected.
 

content/en/blog/_posts/2023-09-26-happy-7th-birthday-kubeadm.md

@@ -31,7 +31,7 @@ To keep kubeadm lean, focused, and vendor/infrastructure agnostic, the following
 Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the
 [Cluster API](https://cluster-api.sigs.k8s.io/). Instead, kubeadm covers only the common denominator
 in every Kubernetes cluster: the
-[control plane](/docs/concepts/overview/components/#control-plane-components).
+[control plane](/docs/concepts/architecture/#control-plane-components).
 The user may install their preferred networking solution and other add-ons on top of Kubernetes
 *after* cluster creation.
 

content/en/blog/_posts/2023-11-07-introducing-sig-etcd.md

@@ -16,7 +16,7 @@ Special Interest Groups (SIGs) are a fundamental part of the Kubernetes project,
 
 ## The critical role of etcd
 
-If we look inside the control plane of a Kubernetes cluster, we will find [etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd), a consistent and highly-available key value store used as Kubernetes' backing store for all cluster data -- this description alone highlights the critical role that etcd plays, and the importance of it within the Kubernetes ecosystem.
+If we look inside the control plane of a Kubernetes cluster, we will find [etcd](https://kubernetes.io/docs/concepts/architecture/#etcd), a consistent and highly-available key value store used as Kubernetes' backing store for all cluster data -- this description alone highlights the critical role that etcd plays, and the importance of it within the Kubernetes ecosystem.
 
 This critical role makes the health of the etcd project and community an important consideration, and [concerns about the state of the project](https://groups.google.com/a/kubernetes.io/g/steering/c/e-O-tVSCJOk/m/N9IkiWLEAgAJ) in early 2022 did not go unnoticed. The changes in the maintainer team, amongst other factors, contributed to a situation that needed to be addressed.
 

content/en/blog/_posts/2024-05-21-sig-node-spotlight/index.md

@@ -62,7 +62,7 @@ with cheap hardware to large AI/ML-optimized GPU-enabled nodes. Nodes may stay o
 maybe be short-lived and be preempted at any moment as they are running on excess compute of a cloud
 provider.
 
-[`kubelet`](/docs/concepts/overview/components/#kubelet) — the
+[`kubelet`](/docs/concepts/architecture/#kubelet) — the
 Kubernetes agent on a node — must work in all these environments reliably. As for the performance
 of kubelet operations, this is becoming increasingly important today. On one hand, as Kubernetes is
 being used on extra small nodes more and more often in telecom and retail environments, it needs to

content/en/docs/concepts/architecture/control-plane-node-communication.md

@@ -120,7 +120,7 @@ up the Konnectivity service in your cluster.
 
 ## {{% heading "whatsnext" %}}
 
-* Read about the [Kubernetes control plane components](/docs/concepts/overview/components/#control-plane-components)
+* Read about the [Kubernetes control plane components](/docs/concepts/architecture/#control-plane-components)
 * Learn more about [Hubs and Spoke model](https://book.kubebuilder.io/multiversion-tutorial/conversion-concepts.html#hubs-spokes-and-other-wheel-metaphors)
 * Learn how to [Secure a Cluster](/docs/tasks/administer-cluster/securing-a-cluster/) 
 * Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/)

content/en/docs/concepts/architecture/controller.md

@@ -161,7 +161,7 @@ controller does.
 
 ## {{% heading "whatsnext" %}}
 
-* Read about the [Kubernetes control plane](/docs/concepts/overview/components/#control-plane-components)
+* Read about the [Kubernetes control plane](/docs/concepts/architecture/#control-plane-components)
 * Discover some of the basic [Kubernetes objects](/docs/concepts/overview/working-with-objects/)
 * Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/)
 * If you want to write your own controller, see

content/en/docs/concepts/architecture/nodes.md

@@ -23,7 +23,7 @@ and contains the services necessary to run
 Typically you have several nodes in a cluster; in a learning or resource-limited
 environment, you might have only one node.
 
-The [components](/docs/concepts/overview/components/#node-components) on a node include the
+The [components](/docs/concepts/architecture/#node-components) on a node include the
 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, a
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}, and the
 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}.
@@ -352,7 +352,7 @@ see the blog-post about [Kubernetes 1.28: NodeSwap graduates to Beta1](/blog/202
 
 Learn more about the following:
 
-* [Components](/docs/concepts/overview/components/#node-components) that make up a node.
+* [Components](/docs/concepts/architecture/#node-components) that make up a node.
 * [API definition for Node](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#node-v1-core).
 * [Node](https://git.k8s.io/design-proposals-archive/architecture/architecture.md#the-kubernetes-node)
   section of the architecture design document.

content/en/docs/concepts/workloads/pods/_index.md

@@ -316,7 +316,7 @@ Pods, the kubelet directly supervises each static Pod (and restarts it if it fai
 
 Static Pods are always bound to one {{< glossary_tooltip term_id="kubelet" >}} on a specific node.
 The main use for static Pods is to run a self-hosted control plane: in other words,
-using the kubelet to supervise the individual [control plane components](/docs/concepts/overview/components/#control-plane-components).
+using the kubelet to supervise the individual [control plane components](/docs/concepts/architecture/#control-plane-components).
 
 The kubelet automatically tries to create a {{< glossary_tooltip text="mirror Pod" term_id="mirror-pod" >}}
 on the Kubernetes API server for each static Pod.

content/en/docs/reference/glossary/container-runtime-interface.md

@@ -17,6 +17,6 @@ The main protocol for the communication between the {{< glossary_tooltip text="k
 
 The Kubernetes Container Runtime Interface (CRI) defines the main
 [gRPC](https://grpc.io) protocol for the communication between the
-[node components](/docs/concepts/overview/components/#node-components)
+[node components](/docs/concepts/architecture/#node-components)
 {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} and
 {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}.

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

@@ -2,7 +2,7 @@
 title: Container runtime interface (CRI)
 id: cri
 date: 2019-03-07
-full_link: /docs/concepts/overview/components/#container-runtime
+full_link: /docs/concepts/architecture/#container-runtime
 short_description: >
     An API for container runtimes to integrate with kubelet
 

content/en/docs/setup/best-practices/multiple-zones.md

@@ -28,7 +28,7 @@ one zone also impairs services in another zone.
 
 ## Control plane behavior
 
-All [control plane components](/docs/concepts/overview/components/#control-plane-components)
+All [control plane components](/docs/concepts/architecture/#control-plane-components)
 support running as a pool of interchangeable resources, replicated per
 component.
 

content/en/docs/setup/production-environment/_index.md

@@ -168,7 +168,7 @@ simply as *nodes*).
 - *Configure nodes*: Nodes can be physical or virtual machines. If you want to
   create and manage your own nodes, you can install a supported operating system,
   then add and run the appropriate
-  [Node services](/docs/concepts/overview/components/#node-components). Consider:
+  [Node services](/docs/concepts/architecture/#node-components). Consider:
   - The demands of your workloads when you set up nodes by having appropriate memory, CPU, and disk speed and storage capacity available.
   - Whether generic computer systems will do or you have workloads that need GPU processors, Windows nodes, or VM isolation.
 - *Validate nodes*: See [Valid node setup](/docs/setup/best-practices/node-conformance/)

content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html

@@ -74,7 +74,7 @@ description: |-
         <div class="row">
             <div class="col-md-8">
                 <p><b>The Control Plane is responsible for managing the cluster.</b> The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p>
-                <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as {{< glossary_tooltip text="containerd" term_id="containerd" >}} or {{< glossary_tooltip term_id="cri-o" >}}. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an <a href="/docs/concepts/overview/components/#etcd">etcd</a> member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.</p>
+                <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as {{< glossary_tooltip text="containerd" term_id="containerd" >}} or {{< glossary_tooltip term_id="cri-o" >}}. A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an <a href="/docs/concepts/architecture/#etcd">etcd</a> member and a control plane instance are lost, and redundancy is compromised. You can mitigate this risk by adding more control plane nodes.</p>
 
             </div>
             <div class="col-md-4">