Merge pull request #34020 from SaumyaBhushan/Issue#34010

Link to release note in older version is broken

Author: k8s-ci-robot

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md

@@ -29,7 +29,7 @@ The upgrade workflow at high level is the following:
 
 ## {{% heading "prerequisites" %}}
 
-- Make sure you read the [release notes]({{< latest-release-notes >}}) carefully.
+- Make sure you read the [release notes](https://git.k8s.io/kubernetes/CHANGELOG) carefully.
 - The cluster should use a static control plane and etcd pods or external etcd.
 - Make sure to back up any important components, such as app-level state stored in a database.
   `kubeadm upgrade` does not touch your workloads, only components internal to Kubernetes, but backups are always a best practice.

content/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md

@@ -58,7 +58,7 @@ The upgrade workflow at high level is the following:
 ## {{% heading "prerequisites" %}}
 
 <!--
-- Make sure you read the [release notes]({{< latest-release-notes >}}) carefully.
+- Make sure you read the [release notes](https://git.k8s.io/kubernetes/CHANGELOG) carefully.
 - The cluster should use a static control plane and etcd pods or external etcd.
 - Make sure to back up any important components, such as app-level state stored in a database.
   `kubeadm upgrade` does not touch your workloads, only components internal to Kubernetes, but backups are always a best practice.