diff --git a/etc/deploy_milvus_on_kubesphere.md b/etc/deploy_milvus_on_kubesphere.md index 2a31e058f..ba51350d2 100644 --- a/etc/deploy_milvus_on_kubesphere.md +++ b/etc/deploy_milvus_on_kubesphere.md @@ -42,7 +42,7 @@ After you make sure your machine meets the conditions, perform the following ste 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. -3. In **Resource List**, click ![three-dots.png](https://kubesphere.io/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png) on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click three-dots.png on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `openpitrix` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. ```yaml @@ -57,15 +57,15 @@ The multi-tenant system of KubeSphere features three levels of hierarchical stru 1. **Create a User**: Click **Platform** in the upper-left corner, and then select **Access Control**. In the left nevigation pane, select **Users**, and click **Create**. In the displayed dialog box, provide all the necessary information (marked with *) and select `platform-regular` for **Role**. Refer to the following image as an example. -![image-20220318172633333](/Users/bennu/Library/Application Support/typora-user-images/image-20220318172633333.png) +image-20220318172633333 2. **Create a workspace**: Select **workspace** in the navigation bar at Access Control, then click **create**, and set the user `milvus-manager` as the workspace Administrator. -![image-20220318172745769](/Users/bennu/Library/Application Support/typora-user-images/image-20220318172745769.png) +image-20220318172745769 3. **Create a project**: Log in to KubeSphere as `milvus-manager` which has the permission to manage the workspace `milvus-ws`. In **Projects**, click **Create**. (A project in KubeSphere is a Kubernetes namespace) -![image-20220318172913153](/Users/bennu/Library/Application Support/typora-user-images/image-20220318172913153.png) +image-20220318172913153 ## Step5: Add Milvus to KubeSphere app repository @@ -83,7 +83,7 @@ The multi-tenant system of KubeSphere features three levels of hierarchical stru 4. Click **install**, a n d under **Basic Information**, set a name for the app. Check the app version and the deployment location, and then click **Next**. -![image-20220318175622525](/Users/bennu/Library/Application Support/typora-user-images/image-20220318175622525.png) +image-20220318175622525 -6. Under **App Settings**, you can edit the configuration file or directly click **Install**. +6. Under **App Settings**, you can edit the configuration file and then directly click **Install**. diff --git a/etc/pic/image-20220318143334767.png b/etc/pic/image-20220318143334767.png new file mode 100644 index 000000000..b6c04fb67 Binary files /dev/null and b/etc/pic/image-20220318143334767.png differ diff --git a/etc/pic/image-20220318143931895.png b/etc/pic/image-20220318143931895.png new file mode 100644 index 000000000..b3fee20da Binary files /dev/null and b/etc/pic/image-20220318143931895.png differ diff --git a/etc/pic/image-20220318172633333.png b/etc/pic/image-20220318172633333.png new file mode 100644 index 000000000..0aa628bdd Binary files /dev/null and b/etc/pic/image-20220318172633333.png differ diff --git a/etc/pic/image-20220318172745769.png b/etc/pic/image-20220318172745769.png new file mode 100644 index 000000000..bc8cd0865 Binary files /dev/null and b/etc/pic/image-20220318172745769.png differ diff --git a/etc/pic/image-20220318172913153.png b/etc/pic/image-20220318172913153.png new file mode 100644 index 000000000..74158410f Binary files /dev/null and b/etc/pic/image-20220318172913153.png differ diff --git a/etc/pic/image-20220318175622525.png b/etc/pic/image-20220318175622525.png new file mode 100644 index 000000000..8cab14e5a Binary files /dev/null and b/etc/pic/image-20220318175622525.png differ