From 35e901cdbf68854bb17a2daae1f5722c00f5df30 Mon Sep 17 00:00:00 2001
From: Matt Cary <34742400+mattcary@users.noreply.github.com>
Date: Thu, 10 Mar 2022 09:47:42 -0800
Subject: [PATCH] Update storage-classes.md

The link to the external provisioner specification had gone stale, it now lives in design-proposals-archive.
---
 content/en/docs/concepts/storage/storage-classes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/storage/storage-classes.md b/content/en/docs/concepts/storage/storage-classes.md
index 421a293737..e46c07df2e 100644
--- a/content/en/docs/concepts/storage/storage-classes.md
+++ b/content/en/docs/concepts/storage/storage-classes.md
@@ -87,7 +87,7 @@ for provisioning PVs. This field must be specified.
 You are not restricted to specifying the "internal" provisioners
 listed here (whose names are prefixed with "kubernetes.io" and shipped
 alongside Kubernetes). You can also run and specify external provisioners,
-which are independent programs that follow a [specification](https://git.k8s.io/community/contributors/design-proposals/storage/volume-provisioning.md)
+which are independent programs that follow a [specification](https://github.com/kubernetes/design-proposals-archive/blob/main/storage/volume-provisioning.md)
 defined by Kubernetes. Authors of external provisioners have full discretion
 over where their code lives, how the provisioner is shipped, how it needs to be
 run, what volume plugin it uses (including Flex), etc. The repository