README: fix Kubernetes releases external link
@@ -18,7 +18,7 @@ CRI-O follows the Kubernetes release cycles with respect to its minor versions
(`1.x.0`). Patch releases (`1.x.y`) for CRI-O are not in sync with those from
Kubernetes, because those are scheduled for each month, whereas CRI-O provides
them only if necessary. If a Kubernetes release goes [End of
-Life](https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md),
+Life](https://github.com/kubernetes/website/blob/main/content/en/releases/patch-releases.md),
then the corresponding CRI-O version can be considered in the same way.
This means that CRI-O also follows the Kubernetes `n-2` release version skew
