mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
wordst
Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
This commit is contained in:
Sherlock113
parent
2585db1227
commit
da99e591a0
|
|
@ -92,7 +92,7 @@ A Pod may be scheduled to other nodes in Kubernetes. For a router, the next hop
|
|||
|
||||
|
||||
|
||||
The image above briefly demonstrates how BGP works in Porter. At the bottom left, it is a two-node Kubernetes cluster with two routers (Leaf1 and Leaf2) above it. These two routers are connected to two kernel switches (Spine layer). Users are on the right side, whose routers are Border1 and Border2 (also connected to Spine).
|
||||
The image above briefly demonstrates how BGP works in Porter. In the bottom-left corner, it is a two-node Kubernetes cluster with two routers (Leaf1 and Leaf2) above it. These two routers are connected to two kernel switches (Spine layer). Users are on the right side, whose routers are Border1 and Border2 (also connected to Spine).
|
||||
|
||||
The three layers of users and Kubernetes server are reachable. Services are created in the Kubernetes cluster and Porter is also used. A VIP (or other manually assigned IP) 1.1.1.1 is assigned by Porter, which sends the information to Leaf1 and Leaf2 through BGP. The next hop to access 1.1.1.1 can be Node1 or Node2. Meanwhile, the Leaf layer also sends the message to the Spine layer, which also knows the next hop to access 1.1.1.1 can be Leaf1 or Leaf2 based on its BGP.
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Alerting and Notification after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -96,7 +96,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `alerting` and `notification` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `alerting` and `notification` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
alerting:
|
||||
|
|
@ -113,7 +113,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable App Store after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `openpitrix` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
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.
|
||||
|
||||
```bash
|
||||
openpitrix:
|
||||
|
|
@ -105,7 +105,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Auditing Logs after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -122,7 +122,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `auditing` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `auditing` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
auditing:
|
||||
|
|
@ -155,7 +155,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable DevOps after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `devops` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `devops` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
devops:
|
||||
|
|
@ -103,7 +103,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Events after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -122,7 +122,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `events` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `events` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
events:
|
||||
|
|
@ -155,7 +155,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Logging after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `logging` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `logging` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
logging:
|
||||
|
|
@ -154,7 +154,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Network Policy after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -93,7 +93,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
networkpolicy:
|
||||
|
|
@ -108,7 +108,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ kubectl apply -f cluster-configuration.yaml
|
|||
|
||||
## Enable Service Mesh after Installation
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
|
||||
|
||||
4. In this yaml file, navigate to `servicemesh` and change `false` to `true` for `enabled`. After you finish, click **Update** at the bottom right corner to save the configuration.
|
||||
4. In this yaml file, navigate to `servicemesh` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
|
||||
|
||||
```bash
|
||||
servicemesh:
|
||||
|
|
@ -101,7 +101,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -38,11 +38,11 @@ After KubeSphere is installed, you need to add different users with varied roles
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
For account security, it is highly recommended that you change your password the first time you log in the console. To change your password, select **User Settings** in the drop-down menu at the top right corner. In **Password Setting**, set a new password.
|
||||
For account security, it is highly recommended that you change your password the first time you log in the console. To change your password, select **User Settings** in the drop-down menu in the top-right corner. In **Password Setting**, set a new password.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
2. After you log in the console, click **Platform** at the top left corner and select **Access Control**.
|
||||
2. After you log in the console, click **Platform** in the top-left corner and select **Access Control**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ Click **OK** after you finish. A newly-created account will display in the accou
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
To log out, click your username at the top right corner and select **Log Out**.
|
||||
To log out, click your username in the top-right corner and select **Log Out**.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ For detailed information about the four accounts you need to create, refer to th
|
|||
|
||||
In this task, you need to create a workspace using the account `ws-manager` created in the previous task. As the basic logic unit for the management of projects, DevOps projects and organization members, workspaces underpin multi-tenant system of KubeSphere.
|
||||
|
||||
1. Log in KubeSphere as `ws-manager` which has the authorization to manage all workspaces on the platform. Click **Platform** at the top left corner. In **Workspaces**, you can see there is only one default workspace **system-workspace** listed, where system-related components and services run. You are not allowed to delete this workspace.
|
||||
1. Log in KubeSphere as `ws-manager` which has the authorization to manage all workspaces on the platform. Click **Platform** in the top-left corner. In **Workspaces**, you can see there is only one default workspace **system-workspace** listed, where system-related components and services run. You are not allowed to delete this workspace.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ Do not copy the content above directly to your local host file. Please replace i
|
|||
|
||||
|
||||
|
||||
6. In the app detail page, click **Normal user** at the bottom left corner.
|
||||
6. In the app detail page, click **Normal user** in the bottom-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
@ -172,7 +172,7 @@ Make sure you replace the project name, IP address and port number in the above
|
|||
|
||||
|
||||
|
||||
### Task 5: View Tracing Details
|
||||
### Task 6: View Tracing Details
|
||||
|
||||
KubeSphere provides the distributed tracing feature based on [Jaeger](https://www.jaegertracing.io/), which is used to monitor and troubleshoot microservices-based distributed applications.
|
||||
|
||||
|
|
@ -184,7 +184,7 @@ KubeSphere provides the distributed tracing feature based on [Jaeger](https://ww
|
|||
|
||||
|
||||
|
||||
### Task 6: Take Over All Traffic
|
||||
### Task 7: Take Over All Traffic
|
||||
|
||||
With the canary release, you can test the new version online by bringing in part of the actual traffic and collect user feedback. If everything runs smoothly without any issues, you can bring all the traffic to the new version.
|
||||
|
||||
|
|
@ -206,7 +206,7 @@ If anything goes wrong with the new version, you can roll back to the previous v
|
|||
|
||||
|
||||
|
||||
### Task 7: Remove the Old Version
|
||||
### Task 8: Remove the Old Version
|
||||
|
||||
Now that the new version v2 takes over all the traffic successfully, you can remove the old version and release the resources of v1 based on your needs.
|
||||
|
||||
|
|
@ -224,4 +224,8 @@ After you remove a certain version, related workloads and Istio-based configurat
|
|||
|
||||
|
||||
|
||||
The above tasks serve as a example of how to adopt a canary release to control traffic and publish a new version of your app. You can also try different strategies in **Grayscale Release** or see related sections in **Project Administration and Usage**.
|
||||
The above tasks serve as a example of how to adopt a canary release to control traffic and publish a new version of your app. You can also try different strategies in **Grayscale Release** or see related sections in **Project Administration and Usage**.
|
||||
|
||||
## Reference
|
||||
|
||||
[Bookinfo Application](https://istio.io/latest/docs/examples/bookinfo/)
|
||||
|
|
@ -83,7 +83,7 @@ Whether you install KubeSphere on Linux or on Kubernetes, you can check the stat
|
|||
|
||||
KubeSphere web console provides a convenient way for users to view and operate on different resources. To enable pluggable components after installation, you only need to make few adjustments in the console directly. For those who are accustomed to the Kubernetes command-line tool, kubectl, they will have no difficulty in using KubeSphere as the tool is integrated into the console.
|
||||
|
||||
1. Log in the console as `admin`. Click **Platform** at the top left corner and select **Clusters Management**.
|
||||
1. Log in the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -113,7 +113,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can find the web kubectl tool by clicking the hammer icon at the bottom right corner of the console.
|
||||
You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ The environment variable `WORDPRESS_DB_PASSWORD` is the password to connect to t
|
|||
|
||||
|
||||
|
||||
2. Enter the basic information (e.g. name it `mysql-secret`) and click **Next**. In the next page, select **Default** for **Type** and click **Add Data** to add a key-value pair. Input the Key (`MYSQL_ROOT_PASSWORD`) and Value (`123456`) as below and click `√` at the bottom right corner to confirm. When you finish, click **Create** to continue.
|
||||
2. Enter the basic information (e.g. name it `mysql-secret`) and click **Next**. In the next page, select **Default** for **Type** and click **Add Data** to add a key-value pair. Input the Key (`MYSQL_ROOT_PASSWORD`) and Value (`123456`) as below and click `√` in the bottom-right corner to confirm. When you finish, click **Create** to continue.
|
||||
|
||||
|
||||
|
||||
|
|
@ -85,7 +85,7 @@ Follow the same steps above to create a WordPress secret `wordpress-secret` with
|
|||
|
||||
|
||||
|
||||
7. Enter `mysql:5.6` in the search box, press **Enter** and click **Use Default Ports**. After that, do not click `√` at the bottom right corner as the setting is not finished yet.
|
||||
7. Enter `mysql:5.6` in the search box, press **Enter** and click **Use Default Ports**. After that, do not click `√` in the bottom-right corner as the setting is not finished yet.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue