KubeSphere CI Bot
GitHub
|
|
@ -1,51 +1,82 @@
|
|||
---
|
||||
title: "Minio App"
|
||||
title: "Deploy MinIO on KubeSphere"
|
||||
keywords: 'Kubernetes, KubeSphere, Minio, app-store'
|
||||
description: 'How to use built-in Minio Object Storage'
|
||||
|
||||
description: 'How to deploy Minio on KubeSphere from the App Store of KubeSphere'
|
||||
linkTitle: "Deploy MinIO on KubeSphere"
|
||||
|
||||
weight: 2242
|
||||
---
|
||||
MinIO object storage is designed for high performence and the S3 API. This guide will show you how to deploy Minio object storage with only a few steps.
|
||||
[MinIO](https://min.io/) object storage is designed for high performance and the S3 API. It is ideal for large, private cloud environments with stringent security requirements and delivers mission-critical availability across a diverse range of workloads.
|
||||
|
||||
This tutorial walks you through an example of deploying MinIO from the App Store of KubeSphere.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- You have enabled [KubeSphere App Store](../../pluggable-components/app-store)
|
||||
- You have completed the tutorial in [Create Workspace, Project, Account and Role](../../quick-start/create-workspace-and-project/). Now switch to use `project-regular` account to log in and enter into `demo-peoject`.
|
||||
- Please make sure you [enable the OpenPitrix system](../../../pluggable-components/app-store/).
|
||||
- You need to create a workspace, a project, and a user account (`project-regular`) for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the `operator` role. In this tutorial, you log in as `project-regular` and work in the project `demo-project` in the workspace `demo-workspace`. For more information, see [Create Workspace, Project, Account and Role](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
||||
### Common steps
|
||||
### Step 1: Deploy MinIO from App Store
|
||||
|
||||
1. Choose Minio template `From App Store`.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Check app info and click `Deploy` button.
|
||||
2. Find MinIO and click **Deploy** on the **App Info** page.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Select app version and deployment location, then go to **Next → Deploy**
|
||||
|
||||
|
||||
|
||||
3. Set a name and select an app version. Make sure MinIO is deployed in `demo-project` and click **Next**.
|
||||
|
||||
4. Wait for a few minutes, then you will see the application minio showing active on the application list.
|
||||
|
||||
|
||||
|
||||
4. In **App Config**, you can use the default configuration or customize the configuration by editing the YAML file directly. Click **Deploy** to continue.
|
||||
|
||||
5. Click into Minio application, and then enter into its service page.
|
||||
|
||||
|
||||
|
||||
5. Wait until MinIO is up and running.
|
||||
|
||||
6. In this page, make sure its deployment and Pod are running, then click **More → Edit Internet Access**, and select **NodePort** in the dropdown list, click **OK** to save it.
|
||||
|
||||
|
||||
|
||||
### Step 2: Access MinIO Browser
|
||||
|
||||
7.Go to **App Template → Configuration Files** and get accessKey and secretKey from `values.yaml`.
|
||||
To access MinIO outside the cluster, you need to expose the app through NodePort first.
|
||||
|
||||
|
||||
1. Go to **Services** and click the service name of MinIO.
|
||||
|
||||
8. In this step, we can access Minio object storage service using ${Node IP}:${NODEPORT}, e.g. http://192.168.18.152:30116/ with the access key and secret key we got previously to login.
|
||||
|
||||
|
||||
|
||||
2. Click **More** and select **Edit Internet Access** from the drop-down menu.
|
||||
|
||||
|
||||
|
||||
3. Select **NodePort** for **Access Method** and click **OK**. For more information, see [Project Gateway](../../../project-administration/project-gateway/).
|
||||
|
||||
|
||||
|
||||
4. Under **Service Ports**, you can see the port is exposed.
|
||||
|
||||
|
||||
|
||||
5. To access the MinIO browser, you need `accessKey` and `secretKey`, which are specified in the configuration file of MinIO. Go to **App Templates** in **Applications**, click MinIO, and you can find the value of these two fields under the tab **Configuration Files**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
6. Access the MinIO browser through `{$NodeIP}:{$Nodeport}` using `accessKey` and `secretKey`.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
You may need to open the port in your security groups and configure related port forwarding rules depending on your where your Kubernetes cluster is deployed.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
7. For more information about MinIO, refer to [the official documentation of MinIO](https://docs.min.io/).
|
||||
|
After Width: | Height: | Size: 456 KiB |
|
After Width: | Height: | Size: 306 KiB |
|
After Width: | Height: | Size: 205 KiB |
|
After Width: | Height: | Size: 290 KiB |
|
After Width: | Height: | Size: 417 KiB |
|
After Width: | Height: | Size: 72 KiB |
|
After Width: | Height: | Size: 70 KiB |
|
After Width: | Height: | Size: 238 KiB |
|
After Width: | Height: | Size: 378 KiB |
|
After Width: | Height: | Size: 384 KiB |
|
After Width: | Height: | Size: 420 KiB |
|
After Width: | Height: | Size: 212 KiB |
|
After Width: | Height: | Size: 287 KiB |
|
After Width: | Height: | Size: 409 KiB |
|
Before Width: | Height: | Size: 192 KiB |
|
Before Width: | Height: | Size: 94 KiB |
|
Before Width: | Height: | Size: 107 KiB |
|
Before Width: | Height: | Size: 88 KiB |
|
Before Width: | Height: | Size: 204 KiB |
|
Before Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 137 KiB |
|
Before Width: | Height: | Size: 118 KiB |