Merge pull request #393 from wenxin-01/master

add app-store docs(rabbitmq,tomcat)
This commit is contained in:
pengfei 2020-10-28 21:58:16 +08:00 committed by GitHub
commit c2e723d12b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
27 changed files with 136 additions and 0 deletions

View File

@ -0,0 +1,64 @@
---
title: "Deploy RabbitMQ on KubeSphere"
keywords: 'KubeSphere, RabbitMQ, Kubernetes, Installation'
description: 'How to deploy RabbitMQ on KubeSphere through App Store'
link title: "Deploy RabbitMQ"
weight: 251
---
[RabbitMQ](https://www.rabbitmq.com/) is the most widely deployed open source message broker. and it's lightweight and easy to deploy on premises and in the cloud. It supports multiple messaging protocols. RabbitMQ can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements.
This tutorial walks you through an example of how to deploy RabbitMQ on KubeSphere.
## Prerequisites
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/). RabbitMQ will be deployed from the App Store.
- You need to create a workspace, a project, and a user account 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-operator` and work in the project `test-project` in the workspace `test-workspace`.
## Hands-on Lab
### Step 1: Deploy RabbitMQ from App Store
Please make sure you are landing on the **Overview** page of the project `test-project`.
1. Go to **App Store**.
![go-to-app-store](/images/docs/rabbitmq-app/rabbitmq01.jpg)
2. Find **RabbitMQ** and click **Deploy**.
![find-tomcat](/images/docs/rabbitmq-app/rabbitmq02.jpg)
![click-deploy](/images/docs/rabbitmq-app/rabbitmq021.jpg)
3. Make sure RabbitMQ is deployed in `test-project` and click **Next**.
![click-next](/images/docs/rabbitmq-app/rabbitmq03.jpg)
4. Use the default configuration or change the account and password as you want. then click **Deploy**.
![click-demploy](/images/docs/rabbitmq-app/rabbitMQ04.jpg)
5. Wait until RabbitMQ is up and running.
![check-if-rabbitmq-is-running](/images/docs/rabbitmq-app/rabbitmq05.jpg)
### Step 2: Access RabbitMQ Dashboard
1. Go to **Services**.and click **rabbiitmq-service-name**.
![go-to-services](/images/docs/rabbitmq-app/rabbitmq06.jpg)
2. Click **More** and click **Edit Internet Access**.
![click-internet](/images/docs/rabbitmq-app/rabbitmq07.jpg)
3. Select **NodePort** and click **Ok**. [More information](https://v2-1.docs.kubesphere.io/docs/project-setting/project-gateway/)
![select-nodeport](/images/docs/rabbitmq-app/rabbitmq08.jpg)
4. Through <font color=green>{$NodeIP} : {$Nodeport}</font> to access rabbitmq management.
![access-rabbitmq](/images/docs/rabbitmq-app/rabbitmq09.png)
5. Log in RabbitMQ management.
![log-in-rabbitmq](/images/docs/rabbitmq-app/rabbitmq10.png)
6. If you want to learn more information about RabbitMQ please refer to https://www.rabbitmq.com/documentation.html.

View File

@ -0,0 +1,72 @@
---
title: "Deploy Tomcat on KubeSphere"
keywords: 'KubeSphere, Kubernetes, Installation, Tomcat'
description: 'How to deploy Tomcat on KubeSphere through App Store'
link title: "Deploy Tomcat"
weight: 261
---
[Apache Tomcat](https://tomcat.apache.org/index.html) software powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.
This tutorial walks you through an example of how to deploy Tomcat on KubeSphere.
## Prerequisites
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/). Tomcat will be deployed from the App Store.
- You need to create a workspace, a project, and a user account 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-operator` and work in the project `test-project` in the workspace `test-workspace`.
## Hands-on Lab
### Step 1: Deploy Tomcat from App Store
Please make sure you are landing on the **Overview** page of the project `test-project`.
1. Go to **App Store**.
![go-to-app-store](/images/docs/tomcat-app/tomcat-app01.jpg)
2. Find **Tomcat** and click **Deploy**.
![find-tomcat](/images/docs/tomcat-app/tomcat-app02.jpg)
![click-deploy](/images/docs/tomcat-app/tomcat-app03.jpg)
3. Make sure MySQL is deployed in `test-project` and click **Next**.
![click-next](/images/docs/tomcat-app/tomcat-app04.jpg)
4. Use the default configuration and click **Deploy**.
![click-demploy](/images/docs/tomcat-app/tomcat-app05.jpg)
5. Wait until Tomcat is up and running.
![check-if-tomcat-is-running](/images/docs/tomcat-app/tomcat-app06.jpg)
### Step 2: Access Tomcat Terminal
1. Go to **Services** and click **tomcat-service-name**.
![click-tomcat-service](/images/docs/tomcat-app/tomcat-app07.jpg)
2. Expand pods information and click **terminal**. You can now use the feature.
![click-container-terminal](/images/docs/tomcat-app/tomcat-app08.jpg)
![tomcat-container-terminal](/images/docs/tomcat-app/tomcat-app09.jpg)
3. You can view the deployed projects in `/usr/local/tomcat/webapps`.
![view-project](/images/docs/tomcat-app/tomcat-app10.jpg)
### Step 3: Access the Tomcat project in the browser
1. Go to **Services** and click **tomcat-service-name**.
2. Click **More** and click **Edit Internet Access**.
![click-edit-internet-access](/images/docs/tomcat-app/tomcat-app11.jpg)
3. Select **NodePort** and click **Ok**. [More information](https://v2-1.docs.kubesphere.io/docs/project-setting/project-gateway/)
![select-nodeport](/images/docs/tomcat-app/tomcat-app12.jpg)
4. Through <font color=green>{$NodeIP} : {$Nodeport} / {$Project path}</font> to access the tomcat project in browser.
![tomcat-port](/images/docs/tomcat-app/tomcat-app13.jpg)
![access-tomcat-browser](/images/docs/tomcat-app/tomcat-app14.jpg)
5. If you want to learn more information about Tomcat please refer to https://tomcat.apache.org/index.html.

Binary file not shown.

After

Width:  |  Height:  |  Size: 248 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 292 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 272 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 253 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 311 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 273 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 300 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 201 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 402 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 109 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 280 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 205 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 232 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 232 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 298 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 274 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 364 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 303 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 151 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 303 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 202 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 257 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 199 KiB