correct manifest path since the file name has been changed in previou…

…sly ccommit
kubernetes-retired · Jun 19, 2021 · 46f65fd · 46f65fd
1 parent ce11f3e
commit 46f65fd
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/virtualcluster/doc/demo.md b/virtualcluster/doc/demo.md
@@ -59,7 +59,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-p
 To create all VirtualCluster components:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/config/setup/all_in_one.yaml
+kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/config/setup/all_in_one_capi.yaml
 ```
 
 Let's check out what we've installed:
@@ -339,7 +339,7 @@ Of course, you can delete all others VirtualCluster objects too to clean up ever
 kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/config/sampleswithspec/clusterversion_v1_nodeport.yaml
 
 # The Virtual Cluster components
-kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/config/setup/all_in_one.yaml
+kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/config/setup/all_in_one_capi.yaml
 
 # The ValidatingWebhookConfiguration which generated runtime and is cluster-scoped resource
 kubectl delete ValidatingWebhookConfiguration virtualcluster-validating-webhook-configuration

diff --git a/virtualcluster/experiment/doc/demo.md b/virtualcluster/experiment/doc/demo.md
@@ -39,7 +39,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-p
 Install vc-manager and vc-scheduler in the vc-manager namespacing using the following command:
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/experiment/config/setup/all_in_one.yaml
+kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-nested/master/virtualcluster/experiment/config/setup/all_in_one_capi.yaml
 ```
 
 Although the per super cluster syncer will be installed in the meta cluster, its configuration relies on the super cluster deployment. We will describe