Replace kubectl's --prune-whitelist with --prune-allowlist

The former is no longer supported in latest kubectl versions.

linkerd.io/content/2-edge/tasks/upgrade.md

@@ -571,9 +571,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.10/tasks/upgrade.md

@@ -90,15 +90,15 @@ resources from the previous version which no longer exist in the new version.
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 ```
 
-Next, run this command again with some `--prune-whitelist` flags added. This is
+Next, run this command again with some `--prune-allowlist` flags added. This is
 necessary to make sure that certain cluster-scoped resources are correctly
 pruned.
 
 ```bash
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 ```
 
 For upgrading a multi-stage installation setup, follow the instructions at
@@ -224,9 +224,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.11/tasks/upgrade.md

@@ -118,15 +118,15 @@ which no longer exist in the new version.
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 ```
 
-Next, run this command again with some `--prune-whitelist` flags added. This is
+Next, run this command again with some `--prune-allowlist` flags added. This is
 necessary to make sure that certain cluster-scoped resources are correctly
 pruned.
 
 ```bash
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 ```
 
 ### With Helm
@@ -340,9 +340,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.12/tasks/upgrade.md

@@ -119,15 +119,15 @@ which no longer exist in the new version.
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 ```
 
-Next, run this command again with some `--prune-whitelist` flags added. This is
+Next, run this command again with some `--prune-allowlist` flags added. This is
 necessary to make sure that certain cluster-scoped resources are correctly
 pruned.
 
 ```bash
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 ```
 
 ### With Helm
@@ -547,9 +547,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.13/tasks/upgrade.md

@@ -560,9 +560,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.14/tasks/upgrade.md

@@ -575,9 +575,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.15/tasks/upgrade.md

@@ -590,9 +590,9 @@ and then invoke those commands through `linkerd viz stat`,
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 # Prune cluster-scoped resources
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 # Install the Linkerd-Viz extension to restore viz functionality.
 linkerd viz install | kubectl apply -f -
 ```

linkerd.io/content/2.9/tasks/upgrade.md

@@ -86,15 +86,15 @@ resources from the previous version which no longer exist in the new version.
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 ```
 
-Next, run this command again with some `--prune-whitelist` flags added. This is
+Next, run this command again with some `--prune-allowlist` flags added. This is
 necessary to make sure that certain cluster-scoped resources are correctly
 pruned.
 
 ```bash
 linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-  --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-  --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+  --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+  --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 ```
 
 For upgrading a multi-stage installation setup, follow the instructions at

linkerd.io/data/cli-2-11.yaml

@@ -1942,9 +1942,9 @@ CLIReference:
 
       # Then run this again to make sure that certain cluster-scoped resources are correctly pruned
       linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-      --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-      --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-      --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+      --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+      --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+      --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
 
       # Similar to install, upgrade may also be broken up into two stages, by user
       # privilege.

linkerd.io/data/cli-2-12.yaml

@@ -1415,16 +1415,16 @@ CLIReference:
     A full list of configurable values can be found at https://www.github.com/linkerd/linkerd2/tree/main/charts/linkerd2/README.md
   Example: |2-
       # Upgrade CRDs first
-      linkerd upgrade --crds | kubectl apply --prune --prune-whitelist=apiextensions.k8s.io/v1/customresourcedefinitions
+      linkerd upgrade --crds | kubectl apply --prune --prune-allowlist=apiextensions.k8s.io/v1/customresourcedefinitions
 
       # Then upgrade the controle-plane and remove linkerd resources that no longer exist in the current version
       linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd -f -
 
       # Then run this again to make sure that certain cluster-scoped resources are correctly pruned
       linkerd upgrade | kubectl apply --prune -l linkerd.io/control-plane-ns=linkerd \
-      --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrole \
-      --prune-whitelist=rbac.authorization.k8s.io/v1/clusterrolebinding \
-      --prune-whitelist=apiregistration.k8s.io/v1/apiservice -f -
+      --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrole \
+      --prune-allowlist=rbac.authorization.k8s.io/v1/clusterrolebinding \
+      --prune-allowlist=apiregistration.k8s.io/v1/apiservice -f -
   InheritedOptions: null
   Name: upgrade
   Options: