mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
SEO with redirect chains
Signed-off-by: liuboaibc <kukudehero@gmail.com>
This commit is contained in:
liuboaibc
parent
3653faaf6a
commit
317784430c
|
|
@ -363,31 +363,31 @@ hasChildren = true
|
|||
[[languages.tr.menu.main]]
|
||||
parent = "Kaynaklar"
|
||||
name = "Open Source Projeler"
|
||||
URL = "projects"
|
||||
URL = "projects/"
|
||||
weight = 1
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
parent = "Kaynaklar"
|
||||
name = "KubeCon & QCon"
|
||||
URL = "conferences"
|
||||
URL = "conferences/"
|
||||
weight = 2
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
parent = "Kaynaklar"
|
||||
name = "Blog Yazıları"
|
||||
URL = "blogs"
|
||||
URL = "blogs/"
|
||||
weight = 3
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
parent = "Kaynaklar"
|
||||
name = "Videolar"
|
||||
URL = "videos"
|
||||
URL = "videos/"
|
||||
weight = 4
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
weight = 4
|
||||
name = "Dokümantasyon"
|
||||
URL = "docs"
|
||||
URL = "docs/"
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
weight = 5
|
||||
|
|
@ -396,17 +396,17 @@ name = "Topluluk"
|
|||
[[languages.tr.menu.main]]
|
||||
parent = "Topluluk"
|
||||
name = "Contribution"
|
||||
URL = "contribution"
|
||||
URL = "contribution/"
|
||||
weight = 1
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
parent = "Topluluk"
|
||||
name = "Case Studies"
|
||||
URL = "case"
|
||||
URL = "case/"
|
||||
weight = 2
|
||||
|
||||
[[languages.tr.menu.main]]
|
||||
parent = "Topluluk"
|
||||
name = "Partnerler"
|
||||
URL = "partner"
|
||||
URL = "partner/"
|
||||
weight = 3
|
||||
|
|
|
|||
|
|
@ -14,27 +14,27 @@ section2:
|
|||
caseList:
|
||||
- icon: "images/case/case5.jpg"
|
||||
content: "Anchnet is a leading Next-generation Cloud Managed Service Provider (Cloud MSP) in China, providing cloud native technologies and solutions for customers."
|
||||
link: "anchnet"
|
||||
link: "anchnet/"
|
||||
|
||||
- icon: "images/case/case3.jpg"
|
||||
content: "Aqara is owned by Lumi United Technology, headquartered in China, with over 300 Aqara service providers and 300 smart home showrooms."
|
||||
link: "aqara"
|
||||
link: "aqara/"
|
||||
|
||||
- icon: "images/case/case1.jpg"
|
||||
content: "Founded in 2012, Benlai is an e-commerce website focused on food, including fruits and vegetables."
|
||||
link: "benlai"
|
||||
link: "benlai/"
|
||||
|
||||
- icon: "images/case/case2.jpg"
|
||||
content: "Huaxia Bank Co., Ltd. is a publicly traded commercial bank in China. It is based in Beijing and was founded in 1992."
|
||||
link: "huaxia-bank"
|
||||
link: "huaxia-bank/"
|
||||
|
||||
- icon: "images/case/maxnerva.jpg"
|
||||
content: "Maxnerva Technology Services, HK.0103 is affiliated and invested by Foxconn Technology Group."
|
||||
link: "maxnerva"
|
||||
link: "maxnerva/"
|
||||
|
||||
- icon: "images/case/vng.jpg"
|
||||
content: "VNG has seen 14 years of continuous development and expansion to become one of the leading IT companies in Vietnam and Southeast Asia."
|
||||
link: "vng"
|
||||
link: "vng/"
|
||||
|
||||
section3:
|
||||
title: 'Various Industries are Powered by KubeSphere'
|
||||
|
|
|
|||
|
|
@ -18,13 +18,13 @@ list:
|
|||
- name: 'Cloud Native Observability: Log Management'
|
||||
summary: As logs often contain very valuable information, log management represents an important part of cloud native observability.
|
||||
author: Benjamin Huo, Dan Ma
|
||||
link: logging
|
||||
link: logging/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200607224942.png
|
||||
|
||||
- name: 'Porter: An Open Source Load Balancer for Kubernetes in a Bare Metal Environment'
|
||||
summary: Porter allows you to create Kubernetes services of type LoadBalancer in bare metal cluster, which makes you enjoy the consistent experience with the cloud.
|
||||
author: Xuetao Song
|
||||
link: porter
|
||||
link: porter/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200611115347.png
|
||||
|
||||
- name: QCon International Software Development Conference
|
||||
|
|
@ -35,7 +35,7 @@ list:
|
|||
- name: 'Development Practices of CSI Storage Plugins - Part Ⅰ'
|
||||
summary: Many users will transfer their apps to Kubernetes, where storage underlies applications. This article focuses on the development practices of Kubernetes storage plugins based on CSI, including the feature, deployment and practice of CSI plugins..
|
||||
author: Xin Wang
|
||||
link: csi
|
||||
link: csi/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200611114611.png
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ section2:
|
|||
- content: 'Quickstart'
|
||||
link: '/docs/quick-start/create-workspace-and-project/'
|
||||
- content: 'Tutorial Videos'
|
||||
link: '../videos'
|
||||
link: '../videos/'
|
||||
|
||||
- name: 'Contribute'
|
||||
icon1: 'images/contribution/contribute.svg'
|
||||
|
|
@ -274,7 +274,7 @@ section4:
|
|||
- title: 'Be an Ambassador'
|
||||
icon: 'images/contribution/group-1.png'
|
||||
content: 'You will be a public-facing community representative. We will provide you with resources to help you be successful as a speaker, or a writer.'
|
||||
link: 'request'
|
||||
link: 'request/'
|
||||
linkContent: 'Become a KubeSphere Ambassador →'
|
||||
|
||||
- title: 'Be a Contributor'
|
||||
|
|
|
|||
|
|
@ -15,16 +15,16 @@ sectionLink:
|
|||
title: Popular Pages
|
||||
description: Learn how to use KubeSphere with these quickstarts, tutorials, and examples.
|
||||
list:
|
||||
- /docs/quick-start/all-in-one-on-linux
|
||||
- /docs/quick-start/minimal-kubesphere-on-k8s
|
||||
- /docs/quick-start/create-workspace-and-project
|
||||
- /docs/introduction/what-is-kubesphere
|
||||
- /docs/pluggable-components
|
||||
- /docs/installing-on-linux/introduction/multioverview
|
||||
- /docs/pluggable-components/app-store
|
||||
- /docs/pluggable-components/devops
|
||||
- /docs/multicluster-management
|
||||
- /docs/project-user-guide/configuration/image-registry
|
||||
- /docs/quick-start/all-in-one-on-linux/
|
||||
- /docs/quick-start/minimal-kubesphere-on-k8s/
|
||||
- /docs/quick-start/create-workspace-and-project/
|
||||
- /docs/introduction/what-is-kubesphere/
|
||||
- /docs/pluggable-components/
|
||||
- /docs/installing-on-linux/introduction/multioverview/
|
||||
- /docs/pluggable-components/app-store/
|
||||
- /docs/pluggable-components/devops/
|
||||
- /docs/multicluster-management/
|
||||
- /docs/project-user-guide/configuration/image-registry/
|
||||
|
||||
videos:
|
||||
title: Popular Videos
|
||||
|
|
|
|||
|
|
@ -40,9 +40,9 @@ Similar to Kubernetes, KubeSphere uses RBAC to manage permissions granted to use
|
|||
|
||||
The access control in KubeSphere is divided into three levels: platform, workspace and project. You use roles to control what permissions users have at different levels for different resources.
|
||||
|
||||
1. [Platform roles](/docs/quick-start/create-workspace-and-project): Control what permissions platform users have for platform resources, such as clusters, workspaces and platform members.
|
||||
2. [Workspace roles](/docs/workspace-administration/role-and-member-management): Control what permissions workspace members have for workspace resources, such as projects (i.e. namespaces) and DevOps projects.
|
||||
3. [Project roles](/docs/project-administration/role-and-member-management): Control what permissions project members have for project resources, such as workloads and pipelines.
|
||||
1. [Platform roles](/docs/quick-start/create-workspace-and-project/): Control what permissions platform users have for platform resources, such as clusters, workspaces and platform members.
|
||||
2. [Workspace roles](/docs/workspace-administration/role-and-member-management/): Control what permissions workspace members have for workspace resources, such as projects (i.e. namespaces) and DevOps projects.
|
||||
3. [Project roles](/docs/project-administration/role-and-member-management/): Control what permissions project members have for project resources, such as workloads and pipelines.
|
||||
|
||||
### Network isolation
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ This chapter contains the glossary that is often used in KubeSphere and the info
|
|||
|
||||
The glossary used in KubeSphere.
|
||||
|
||||
## [KubeSphere API](../api-reference/api-docs)
|
||||
## [KubeSphere API](../api-reference/api-docs/)
|
||||
|
||||
The REST API is the fundamental fabric of KubeSphere. This guide shows you how to access the KubeSphere API server.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ You need an account granted a role including the authorization of **Clusters Man
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ You can use Elasticsearch, Kafka and Fluentd as log receivers in KubeSphere. Thi
|
|||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. On the **Cluster Management** page, go to **Log Collections** in **Cluster Settings**.
|
||||
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ EOF
|
|||
## Step 2: Add Fluentd as a Log Receiver (i.e. Collector)
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
3. On the **Cluster Management** page, go to **Log Collections** in **Cluster Settings**.
|
||||
|
||||
4. Click **Add Log Collector** and choose **Fluentd**.
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ You can use [strimzi-kafka-operator](https://github.com/strimzi/strimzi-kafka-op
|
|||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. On the **Cluster Management** page, go to **Log Collections** in **Cluster Settings**.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ To add a log receiver:
|
|||
|
||||
2. Click **Platform** in the top left corner and select **Clusters Management**.
|
||||
|
||||
3. If you have enabled the [multi-cluster feature](../../../../multicluster-management), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
3. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
4. Go to **Log Collections** in **Cluster Settings**.
|
||||
|
||||
|
|
@ -51,11 +51,11 @@ If the default Elasticsearch log receiver is deleted, refer to [Add Elasticsearc
|
|||
|
||||
### Add Kafka as a log receiver
|
||||
|
||||
Kafka is often used to receive logs and serves as a broker to other processing systems like Spark. [Add Kafka as a Receiver](../add-kafka-as-receiver) demonstrates how to add Kafka to receive Kubernetes logs.
|
||||
Kafka is often used to receive logs and serves as a broker to other processing systems like Spark. [Add Kafka as a Receiver](../add-kafka-as-receiver/) demonstrates how to add Kafka to receive Kubernetes logs.
|
||||
|
||||
### Add Fluentd as a log receiver
|
||||
|
||||
If you need to output logs to more places other than Elasticsearch or Kafka, you can add Fluentd as a log receiver. Fluentd has numerous output plugins which can forward logs to various destinations such as S3, MongoDB, Cassandra, MySQL, syslog, and Splunk. [Add Fluentd as a Receiver](../add-fluentd-as-receiver) demonstrates how to add Fluentd to receive Kubernetes logs.
|
||||
If you need to output logs to more places other than Elasticsearch or Kafka, you can add Fluentd as a log receiver. Fluentd has numerous output plugins which can forward logs to various destinations such as S3, MongoDB, Cassandra, MySQL, syslog, and Splunk. [Add Fluentd as a Receiver](../add-fluentd-as-receiver/) demonstrates how to add Fluentd to receive Kubernetes logs.
|
||||
|
||||
## Add a Log Receiver (i.e. Collector) for Events or Auditing Logs
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ You need an account granted a role including the authorization of **Clusters Man
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -34,4 +34,4 @@ This is not convenient for Kubernetes users and it breaks the multi-tenant princ
|
|||
|
||||
To use Alertmanager to manage alerts on the platform, KubeSphere offers [Notification Manager](https://github.com/kubesphere/notification-manager), a Kubernetes native notification management tool, which is completely open source. It complies with the multi-tenancy principle, providing user-friendly experiences of Kubernetes notifications. It's installed by default in KubeSphere v3.0 and above.
|
||||
|
||||
For more details about using Notification Manager to receive Alertmanager notifications, refer to [Notification Manager](../notification-manager).
|
||||
For more details about using Notification Manager to receive Alertmanager notifications, refer to [Notification Manager](../notification-manager/).
|
||||
|
|
@ -23,7 +23,7 @@ Cluster nodes are only accessible to cluster administrators. Some node metrics a
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ You need an account granted a role including the authorization of **Clusters Man
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management) with member clusters imported, you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. On the **Cluster Management** page, navigate to **Storage Classes** under **Storage**, where you can create, update and delete a storage class.
|
||||
|
||||
|
|
|
|||
|
|
@ -79,7 +79,7 @@ In this example, all workloads are deployed in `kubesphere-sample-dev`. You must
|
|||
|
||||
### Create a pipeline for the Maven project
|
||||
|
||||
1. Go to **Pipelines** of your DevOps project and click **Create**. For more information, see [Create a Pipeline - using Graphical Editing Panel](../../how-to-use/create-a-pipeline-using-graphical-editing-panel).
|
||||
1. Go to **Pipelines** of your DevOps project and click **Create**. For more information, see [Create a Pipeline - using Graphical Editing Panel](../../how-to-use/create-a-pipeline-using-graphical-editing-panel/).
|
||||
|
||||
2. Go to the detail page of the pipeline and click **Edit Jenkinsfile**.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 11410
|
|||
|
||||
- You need to [enable the KubeSphere DevOps System](../../../../docs/pluggable-components/devops/).
|
||||
- You need to have a [Docker Hub](https://hub.docker.com/) account.
|
||||
- You need to create a workspace, a DevOps project, a project, and an account (`project-regular`). This account needs to be invited to the DevOps project and the project for deploying your workload with the role `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a DevOps project, a project, and an account (`project-regular`). This account needs to be invited to the DevOps project and the project for deploying your workload with the role `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a Docker Hub Access Token
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ weight: 11420
|
|||
- You need to [enable the multi-cluster feature](../../../../docs/multicluster-management/).
|
||||
- You need to have a [Docker Hub](https://hub.docker.com/) account.
|
||||
- You need to [enable the KubeSphere DevOps System](../../../../docs/pluggable-components/devops/) on your host cluster.
|
||||
- You need to create a workspace with multiple clusters, a DevOps project on your **host** cluster, a multi-cluster project (in this tutorial, this multi-cluster project is created on the host cluster and one member cluster), and an account (`project-regular`). This account needs to be invited to the DevOps project and the multi-cluster project with the role `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project), [Multi-cluster Management](../../../multicluster-management) and [Multi-cluster Projects](../../../project-administration/project-and-multicluster-project/#multi-cluster-projects).
|
||||
- You need to create a workspace with multiple clusters, a DevOps project on your **host** cluster, a multi-cluster project (in this tutorial, this multi-cluster project is created on the host cluster and one member cluster), and an account (`project-regular`). This account needs to be invited to the DevOps project and the multi-cluster project with the role `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/), [Multi-cluster Management](../../../multicluster-management/) and [Multi-cluster Projects](../../../project-administration/project-and-multicluster-project/#multi-cluster-projects).
|
||||
|
||||
## Create a Docker Hub Access Token
|
||||
|
||||
|
|
|
|||
|
|
@ -279,6 +279,6 @@ You need a SonarQube token so that your pipeline can communicate with SonarQube
|
|||
|
||||
## View Results on the KubeSphere Console
|
||||
|
||||
After you [create a pipeline using the graphical editing panel](../../how-to-use/create-a-pipeline-using-graphical-editing-panel) or [create a pipeline using a Jenkinsfile](../../how-to-use/create-a-pipeline-using-jenkinsfile), you can view the result of code quality analysis. For example, you may see an image as below if SonarQube runs successfully.
|
||||
After you [create a pipeline using the graphical editing panel](../../how-to-use/create-a-pipeline-using-graphical-editing-panel/) or [create a pipeline using a Jenkinsfile](../../how-to-use/create-a-pipeline-using-jenkinsfile/), you can view the result of code quality analysis. For example, you may see an image as below if SonarQube runs successfully.
|
||||
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to create a pipeline based on a Jenkinsfile from
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
Two types of pipelines can be created in KubeSphere: Pipelines created based on a Jenkinsfile in SCM, which is introduced in this tutorial, and [pipelines created through the graphical editing panel](../create-a-pipeline-using-graphical-editing-panel). The Jenkinsfile in SCM requires an internal Jenkinsfile in Source Control Management (SCM). In other words, the Jenkfinsfile serves as part of SCM. The KubeSphere DevOps system automatically builds a CI/CD pipeline based on the existing Jenkinsfile of the code repository. You can define workflows such as `stage` and `step`.
|
||||
Two types of pipelines can be created in KubeSphere: Pipelines created based on a Jenkinsfile in SCM, which is introduced in this tutorial, and [pipelines created through the graphical editing panel](../create-a-pipeline-using-graphical-editing-panel/). The Jenkinsfile in SCM requires an internal Jenkinsfile in Source Control Management (SCM). In other words, the Jenkfinsfile serves as part of SCM. The KubeSphere DevOps system automatically builds a CI/CD pipeline based on the existing Jenkinsfile of the code repository. You can define workflows such as `stage` and `step`.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Currently, you can store the following 4 types of credentials in a DevOps projec
|
|||
- **Secret Text**: Secret content in a file.
|
||||
- **kubeconfig**: It is used to configure cross-cluster authentication. If you select this type, the dialog will auto-populate the field with the kubeconfig file of the current Kubernetes cluster.
|
||||
|
||||
This tutorial demonstrates how to create and manage credentials in a DevOps project. For more information about how credentials are used, see [Create a Pipeline Using a Jenkinsfile](../create-a-pipeline-using-jenkinsfile/) and [Create a Pipeline Using Graphical Editing Panels](../create-a-pipeline-using-graphical-editing-panel).
|
||||
This tutorial demonstrates how to create and manage credentials in a DevOps project. For more information about how credentials are used, see [Create a Pipeline Using a Jenkinsfile](../create-a-pipeline-using-jenkinsfile/) and [Create a Pipeline Using Graphical Editing Panels](../create-a-pipeline-using-graphical-editing-panel/).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
@ -84,4 +84,4 @@ A file that is used to configure access to clusters is called a kubeconfig file.
|
|||
|
||||
[Create a Pipeline Using a Jenkinsfile](../create-a-pipeline-using-jenkinsfile/)
|
||||
|
||||
[Create a Pipeline Using Graphical Editing Panels](../create-a-pipeline-using-graphical-editing-panel)
|
||||
[Create a Pipeline Using Graphical Editing Panels](../create-a-pipeline-using-graphical-editing-panel/)
|
||||
|
|
@ -20,7 +20,7 @@ The built-in Jenkins cannot share the same email configuration with the platform
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. Go to **Workloads** under **Application Workloads**, and choose the project **kubesphere-devops-system** from the drop-down list. Click the three dots on the right of **ks-jenkins** to edit its YAML.
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ It is recommended that you configure Jenkins in KubeSphere through Configuration
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management) with member clusters imported, you can select a specific cluster to edit the ConfigMap. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management/) with member clusters imported, you can select a specific cluster to edit the ConfigMap. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. From the navigation bar, select **ConfigMaps** under **Configurations**. On the **ConfigMaps** page, select `kubesphere-devops-system` from the drop-down list and click `jenkins-casc-config`.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ You need an account granted a role including the authorization of **Clusters Man
|
|||
|
||||
|
||||
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
2. If you have enabled the [multi-cluster feature](../../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. Navigate to **Cluster Nodes** under **Nodes**, where you can see existing nodes in the current cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@ Similar to installing KubeSphere on an existing Kubernetes cluster in an online
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can enable pluggable components in this YAML file to explore more features of KubeSphere. Refer to [Enable Pluggle Components](../../../pluggable-components) for more details.
|
||||
You can enable pluggable components in this YAML file to explore more features of KubeSphere. Refer to [Enable Pluggle Components](../../../pluggable-components/) for more details.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -381,7 +381,7 @@ spec:
|
|||
|
||||
{{< notice info >}}
|
||||
|
||||
For more information about these parameters, see [Multi-node Installation](../multioverview/#2-edit-the-configuration-file) and [Kubernetes Cluster Configuration](../vars/). To enable pluggable components in `config-sample.yaml`, refer to [Enable Pluggle Components](../../../pluggable-components) for more details.
|
||||
For more information about these parameters, see [Multi-node Installation](../multioverview/#2-edit-the-configuration-file) and [Kubernetes Cluster Configuration](../vars/). To enable pluggable components in `config-sample.yaml`, refer to [Enable Pluggle Components](../../../pluggable-components/) for more details.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Here is a list of available installation options.
|
|||
|
||||
- [All-in-one installation](../../../quick-start/all-in-one-on-linux/): Install KubeSphere on a single node. It is only for users to quickly get familiar with KubeSphere.
|
||||
- [Multi-node installation](../multioverview/): Install KubeSphere on multiple nodes. It is for testing or development.
|
||||
- [Air-gapped installation on Linux](../air-gapped-installation): All images of KubeSphere have been encapsulated into a package. It is convenient for air-gapped installation on Linux machines.
|
||||
- [Air-gapped installation on Linux](../air-gapped-installation/): All images of KubeSphere have been encapsulated into a package. It is convenient for air-gapped installation on Linux machines.
|
||||
- [High availability installation](../../../installing-on-linux/high-availability-configurations/ha-configuration/): Install a highly-available KubeSphere cluster with multiple nodes which is used for the production environment.
|
||||
- Minimal Packages: Only install the minimum required system components of KubeSphere. Here is the minimum resource requirement:
|
||||
- 2 CPUs
|
||||
|
|
@ -36,7 +36,7 @@ If you have an existing Kubernetes cluster, see [Overview of Installing on Kuber
|
|||
- For all-in-one installation, the only one node is both the master and the worker.
|
||||
- For multi-node installation, you need to provide host information in a configuration file.
|
||||
- Your Linux host must have OpenSSH Server installed.
|
||||
- See [Port Requirements](../port-firewall) before installation.
|
||||
- See [Port Requirements](../port-firewall/) before installation.
|
||||
|
||||
## KubeKey
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ The separate configuration file contains all parameters of GlusterFS storage whi
|
|||
|
||||
## Step 3: Download KubeKey
|
||||
|
||||
Follow the steps below to download [KubeKey](../../../installing-on-linux/introduction/kubekey) on the taskbox.
|
||||
Follow the steps below to download [KubeKey](../../../installing-on-linux/introduction/kubekey/) on the taskbox.
|
||||
|
||||
{{< tabs >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ weight: 1500
|
|||
|
||||
## Separation of frontend and backend
|
||||
|
||||
KubeSphere separates [frontend](https://github.com/kubesphere/console) from [backend](https://github.com/kubesphere/kubesphere), and it itself is a cloud native application and provides open standard REST APIs for external systems to use. Please see [API documentation](../../api-reference/api-docs) for details. The following figure is the system architecture. KubeSphere can run anywhere from on-premise datacenter to any cloud to edge. In addition, it can be deployed on any Kubernetes distribution.
|
||||
KubeSphere separates [frontend](https://github.com/kubesphere/console) from [backend](https://github.com/kubesphere/kubesphere), and it itself is a cloud native application and provides open standard REST APIs for external systems to use. Please see [API documentation](../../api-reference/api-docs/) for details. The following figure is the system architecture. KubeSphere can run anywhere from on-premise datacenter to any cloud to edge. In addition, it can be deployed on any Kubernetes distribution.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 5220
|
|||
|
||||
The component [Tower](https://github.com/kubesphere/tower) of KubeSphere is used for agent connection. Tower is a tool for network connection between clusters through the agent. If the Host Cluster (H Cluster) cannot access the Member Cluster (M Cluster) directly, you can expose the proxy service address of the H cluster. This enables the M Cluster to connect to the H Cluster through the agent. This method is applicable when the M Cluster is in a private environment (e.g. IDC) and the H Cluster is able to expose the proxy service. The agent connection is also applicable when your clusters are distributed across different cloud providers.
|
||||
|
||||
To use the multi-cluster feature using an agent, you must have at least two clusters serving as the H Cluster and the M Cluster respectively. A cluster can be defined as the H Cluster or the M Cluster either before or after you install KubeSphere. For more information about installing KubeSphere, refer to [Installing on Linux](../../../installing-on-linux) and [Installing on Kubernetes](../../../installing-on-kubernetes).
|
||||
To use the multi-cluster feature using an agent, you must have at least two clusters serving as the H Cluster and the M Cluster respectively. A cluster can be defined as the H Cluster or the M Cluster either before or after you install KubeSphere. For more information about installing KubeSphere, refer to [Installing on Linux](../../../installing-on-linux/) and [Installing on Kubernetes](../../../installing-on-kubernetes/).
|
||||
|
||||
## Video Demonstration
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 5210
|
|||
|
||||
If the kube-apiserver address of the Member Cluster (M Cluster) is accessible on any node of the Host Cluster (H Cluster), you can adopt **Direction Connection**. This method is applicable when the kube-apiserver address of the M Cluster can be exposed or H Cluster and M Cluster are in the same private network or subnet.
|
||||
|
||||
To use the multi-cluster feature using direct connection, you must have at least two clusters serving as the H Cluster and the M Cluster respectively. A cluster can be defined as the H Cluster or the M Cluster either before or after you install KubeSphere. For more information about installing KubeSphere, refer to [Installing on Linux](../../../installing-on-linux) and [Installing on Kubernetes](../../../installing-on-kubernetes).
|
||||
To use the multi-cluster feature using direct connection, you must have at least two clusters serving as the H Cluster and the M Cluster respectively. A cluster can be defined as the H Cluster or the M Cluster either before or after you install KubeSphere. For more information about installing KubeSphere, refer to [Installing on Linux](../../../installing-on-linux/) and [Installing on Kubernetes](../../../installing-on-kubernetes/).
|
||||
|
||||
## Video Demonstration
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 6600
|
|||
|
||||
Alerting and Notification are two important building blocks of observability, closely related to monitoring and logging. The alerting system in KubeSphere, coupled with the proactive failure notification system, allows users to know activities of interest based on alerting policies. When a predefined threshold of a certain metric is reached, an alert will be sent to preconfigured recipients, the notification method of which can be set by yourself, including Email, WeChat Work and Slack. With a highly functional alerting and notification system in place, you can quickly identify and resolve potential issues in advance before they affect your business.
|
||||
|
||||
For more information, see [Alerting Policy](../../project-user-guide/alerting/alerting-policy) and [Alerting Message](../../project-user-guide/alerting/alerting-message).
|
||||
For more information, see [Alerting Policy](../../project-user-guide/alerting/alerting-policy/) and [Alerting Message](../../project-user-guide/alerting/alerting-message/).
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 6700
|
|||
|
||||
KubeSphere Auditing Log System provides a security-relevant chronological set of records documenting the sequence of activities related to individual users, managers, or other components of the system. Each request to KubeSphere generates an event that is then written to a webhook and processed according to a certain rule.
|
||||
|
||||
For more information, see [Auditing Log Query](../../toolbox/auditing/auditing-query).
|
||||
For more information, see [Auditing Log Query](../../toolbox/auditing/auditing-query/).
|
||||
|
||||
## Enable Auditing Logs before Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 6500
|
|||
|
||||
KubeSphere events allow users to keep track of what is happening inside a cluster, such as node scheduling status and image pulling result. They will be accurately recorded with the specific reason, status and message displayed in the web console. To query events, users can quickly launch the web Toolkit and enter related information in the search bar with different filters (e.g keyword and project) available. Events can also be archived to third-party tools, such as Elasticsearch, Kafka or Fluentd.
|
||||
|
||||
For more information, see [Event Query](../../toolbox/events-query).
|
||||
For more information, see [Event Query](../../toolbox/events-query/).
|
||||
|
||||
## Enable Events before Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 6400
|
|||
|
||||
KubeSphere provides a powerful, holistic and easy-to-use logging system for log collection, query and management. It covers logs at varied levels, including tenants, infrastructure resources, and applications. Users can search logs from different dimensions, such as project, workload, Pod and keyword. Compared with Kibana, the tenant-based logging system of KubeSphere features better isolation and security among tenants as tenants can only view their own logs. Apart from KubeSphere's own logging system, the container platform also allows users to add third-party log collectors, such as Elasticsearch, Kafka and Fluentd.
|
||||
|
||||
For more information, see [Log Query](../../toolbox/log-query).
|
||||
For more information, see [Log Query](../../toolbox/log-query/).
|
||||
|
||||
## Enable Logging before Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ weight: 6800
|
|||
|
||||
On the basis of [Istio](https://istio.io/), KubeSphere Service Mesh visualizes microservices governance and traffic management. It features a powerful toolkit including **circuit breaking, blue-green deployment, canary release, traffic mirroring, distributed tracing, observability and traffic control**. Developers can easily get started with KubeSphere Service Mesh without any code hacking, with the learning curve of Istio greatly reduced. All features of KubeSphere Service Mesh are designed to meet users' demand for their business.
|
||||
|
||||
For more information, see [Grayscale Release](../../project-user-guide/grayscale-release/overview).
|
||||
For more information, see [Grayscale Release](../../project-user-guide/grayscale-release/overview/).
|
||||
|
||||
## Enable KubeSphere Service Mesh before Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to collect disk logs for an example app.
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- You need to create a workspace, a project and an account (`project-admin`). The account must be invited to the project with the role of `admin` at the project level. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-admin`). The account must be invited to the project with the role of `admin` at the project level. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../quick-start/create-workspace-and-project/).
|
||||
- You need to enable [the KubeSphere Logging System](../../pluggable-components/logging/).
|
||||
|
||||
## Enable Disk Log Collection
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ This tutorial demonstrates how to set a gateway in KubeSphere for the external a
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-admin`). The account must be invited to the project with the role of `admin` at the project level. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../docs/quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-admin`). The account must be invited to the project with the role of `admin` at the project level. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../docs/quick-start/create-workspace-and-project/).
|
||||
|
||||
## Set a Gateway
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This tutorial demonstrates how to view alerting messages at the workload level.
|
|||
## Prerequisites
|
||||
|
||||
- You have enabled [KubeSphere Alerting and Notification](../../../pluggable-components/alerting-notification/).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
- You have created a workload-level alerting policy and received alert notifications of it. If it is not ready, refer to [Alerting Policy (Workload Level)](../alerting-policy/) to create one first.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ KubeSphere provides alerting policies for nodes and workloads. This tutorial dem
|
|||
|
||||
- You have enabled [KubeSphere Alerting and Notification](../../../pluggable-components/alerting-notification/).
|
||||
- You have configured the [Mail server](../../../cluster-administration/cluster-settings/mail-server/).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- You have workloads in this project. If they are not ready, go to **Applications** under **Application Workloads**, and click **Deploy Sample Application** to deploy an application quickly. For more information, see [Deploy Bookinfo and Manage Traffic](../../../quick-start/deploy-bookinfo-to-k8s/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ For more information, see [the official documentation of Kubernetes](https://kub
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a CronJob
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ DaemonSets are very helpful in cases where you want to deploy ongoing background
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a DaemonSet
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ For more information, see the [official documentation of Kubernetes](https://kub
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a Deployment
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ The following example demonstrates specific steps of creating a Job (computing
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a Job
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In KubeSphere, stateful and stateless Services are created with a virtual IP by
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Service Types
|
||||
|
||||
|
|
@ -36,11 +36,11 @@ As shown in the image below, KubeSphere provides three basic methods to create a
|
|||
|
||||
- **Stateless Service**
|
||||
|
||||
Stateless Services are the most commonly used Services in container services. They define the Pod template to control the Pod status, including rolling updates and rollbacks. A **Deployment** workload is also created when you create a stateless Service. For more information about stateless Services, see [Deployments](../../application-workloads/deployments).
|
||||
Stateless Services are the most commonly used Services in container services. They define the Pod template to control the Pod status, including rolling updates and rollbacks. A **Deployment** workload is also created when you create a stateless Service. For more information about stateless Services, see [Deployments](../../application-workloads/deployments/).
|
||||
|
||||
- **Stateful Service**
|
||||
|
||||
Stateful Services are used to manage stateful applications, ensuring ordered and graceful deployment and scaling. They also provide stable persistent storage and network identifiers. A **StatefulSet** workload is also created when you create a stateful Service. For more information about stateful Services, see [StatefulSets](../../application-workloads/statefulsets).
|
||||
Stateful Services are used to manage stateful applications, ensuring ordered and graceful deployment and scaling. They also provide stable persistent storage and network identifiers. A **StatefulSet** workload is also created when you create a stateful Service. For more information about stateful Services, see [StatefulSets](../../application-workloads/statefulsets/).
|
||||
|
||||
- **External Service**
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ For more information, see the [official documentation of Kubernetes](https://kub
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a StatefulSet
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to quickly deploy [NGINX](https://www.nginx.com/)
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- You have enabled [OpenPitirx (App Store)](../../../pluggable-components/app-store).
|
||||
- You have enabled [OpenPitirx (App Store)](../../../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 invited to the project with the `operator` role. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to quickly deploy [Grafana](https://grafana.com/)
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- You have enabled [OpenPitirx (App Store)](../../../pluggable-components/app-store).
|
||||
- You have enabled [OpenPitirx (App Store)](../../../pluggable-components/app-store/).
|
||||
- You have completed the tutorial of [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/). Namely, you must have a workspace, a project and two user accounts (`ws-admin` and `project-regular`). `ws-admin` must be granted the role of `workspace-admin` in the workspace and `project-regular` must be granted the role of `operator` in the project.
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ This tutorial demonstrates how to create a ConfigMap in KubeSphere.
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a ConfigMap
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to create Secrets for different image registries.
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a Secret
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ This tutorial demonstrates how to create a Secret in KubeSphere.
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Create a Secret
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Directly exposing Prometheus metrics from applications is a common way among clo
|
|||
|
||||
The Prometheus community offers client libraries for most programming languages. Find your language on the [Prometheus Client Libraries](https://prometheus.io/docs/instrumenting/clientlibs/) page. For Go developers, read [Instrumenting a Go application](https://prometheus.io/docs/guides/go-application/) to learn how to write a Prometheus-compliant application.
|
||||
|
||||
The [sample web application](../examples/monitor-sample-web) is an example demonstrating how an application exposes Prometheus-formatted metrics directly.
|
||||
The [sample web application](../examples/monitor-sample-web/) is an example demonstrating how an application exposes Prometheus-formatted metrics directly.
|
||||
|
||||
#### Indirect exposing
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ If you don’t want to modify your code or you cannot do so because the applicat
|
|||
|
||||
For most third-party applications, such as MySQL, the Prometheus community provides production-ready exporters. Refer to [Exporters and Integrations](https://prometheus.io/docs/instrumenting/exporters/) for available exporters. In KubeSphere, it is recommended to [enable OpenPitrix](../../../pluggable-components/app-store/) and deploy exporters from the App Store. Exporters for MySQL, Elasticsearch, and Redis are all built-in apps in the App Store.
|
||||
|
||||
Please read [Monitor MySQL](../examples/monitor-mysql) to learn how to deploy a MySQL exporter and monitor MySQL metrics.
|
||||
Please read [Monitor MySQL](../examples/monitor-mysql/) to learn how to deploy a MySQL exporter and monitor MySQL metrics.
|
||||
|
||||
Writing an exporter is nothing short of instrumenting an application with Prometheus client libraries. The only difference is that exporters need to connect to applications and translate application metrics into Prometheus format.
|
||||
|
||||
|
|
@ -44,10 +44,10 @@ The ServiceMonitor CRD is defined by [Prometheus Operator](https://github.com/pr
|
|||
|
||||
In KubeSphere v3.0.0, you need to pack ServiceMonitor with your applications (or exporters) into a Helm chart for reuse. In future releases, KubeSphere will provide graphical interfaces for easy operation.
|
||||
|
||||
Please read [Monitor a Sample Web Application](../examples/monitor-sample-web) to learn how to pack ServiceMonitor with your application.
|
||||
Please read [Monitor a Sample Web Application](../examples/monitor-sample-web/) to learn how to pack ServiceMonitor with your application.
|
||||
|
||||
### Step 3: Visualize Metrics
|
||||
|
||||
Around two minutes, the KubeSphere monitoring engine starts to scape and store metrics. Then you can use PromQL to query metrics and design panels and dashboards.
|
||||
|
||||
Please read [Querying](../visualization/querying) to learn how to write a PromQL expression. For dashboard features, please read [Visualization](../visualization/overview).
|
||||
Please read [Querying](../visualization/querying/) to learn how to write a PromQL expression. For dashboard features, please read [Visualization](../visualization/overview/).
|
||||
|
|
@ -6,7 +6,7 @@ linkTitle: "Overview"
|
|||
weight: 10815
|
||||
---
|
||||
|
||||
This section introduces monitoring dashboard features. You will learn how to visualize metric data in KubeSphere for your custom apps. If you do not know how to integrate your app metrics into the KubeSphere monitoring system, read [Introduction](../../introduction) first.
|
||||
This section introduces monitoring dashboard features. You will learn how to visualize metric data in KubeSphere for your custom apps. If you do not know how to integrate your app metrics into the KubeSphere monitoring system, read [Introduction](../../introduction/) first.
|
||||
|
||||
## Create a Monitoring Dashboard
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ The blue-green release provides a zero downtime deployment, which means the new
|
|||
## Prerequisites
|
||||
|
||||
- You need to enable [KubeSphere Service Mesh](../../../pluggable-components/service-mesh/).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- You need to enable **Application Governance** and have an available app so that you can implement the blue-green deployment for it. The sample app used in this tutorial is Bookinfo. For more information, see [Deploy Bookinfo and Manage Traffic](../../../quick-start/deploy-bookinfo-to-k8s/).
|
||||
|
||||
## Create a Blue-green Deployment Job
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ This method serves as an efficient way to test performance and reliability of a
|
|||
## Prerequisites
|
||||
|
||||
- You need to enable [KubeSphere Service Mesh](../../../pluggable-components/service-mesh/).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- You need to enable **Application Governance** and have an available app so that you can implement the canary release for it. The sample app used in this tutorial is Bookinfo. For more information, see [Deploy and Access Bookinfo](../../../quick-start/deploy-bookinfo-to-k8s/).
|
||||
|
||||
## Step 1: Create a Canary Release Job
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ Traffic mirroring, also called shadowing, is a powerful, risk-free method of tes
|
|||
## Prerequisites
|
||||
|
||||
- You need to enable [KubeSphere Service Mesh](../../../pluggable-components/service-mesh/).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- You need to enable **Application Governance** and have an available app so that you can mirror the traffic of it. The sample app used in this tutorial is Bookinfo. For more information, see [Deploy Bookinfo and Manage Traffic](../../../quick-start/deploy-bookinfo-to-k8s/).
|
||||
|
||||
## Create a Traffic Mirroring Job
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ For demonstration and testing purposes, here are some example artifacts you can
|
|||
|
||||
- You have enabled the [KubeSphere DevOps System](../../../pluggable-components/devops/).
|
||||
- You need to create a [Docker Hub](http://www.dockerhub.com/) account. GitLab and Harbor are also supported.
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- Set a CI dedicated node for building images. This is not mandatory but recommended for the development and production environment as it caches dependencies and reduces build time. For more information, see [Set a CI Node for Dependency Caching](../../../devops-user-guide/how-to-use/set-ci-node/).
|
||||
|
||||
## Create a Service Using Binary-to-Image (B2I)
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ This tutorial demonstrates how to use S2I to import source code of a Java sample
|
|||
|
||||
- You need to enable the [KubeSphere DevOps System](../../../pluggable-components/devops/) as S2I is integrated into it.
|
||||
- You need to create a [GitHub](https://github.com/) account and a [Docker Hub](http://www.dockerhub.com/) account. GitLab and Harbor are also supported. This tutorial uses a GitHub repository to provide the source code for building and pushes an image to Docker Hub.
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
- Set a CI dedicated node for building images. This is not mandatory but recommended for the development and production environment as it caches dependencies and reduces build time. For more information, see [Set a CI Node for Dependency Caching](../../../devops-user-guide/how-to-use/set-ci-node/).
|
||||
|
||||
## Use Source-to-Image (S2I)
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to create and use a volume snapshot.
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
- Kubernetes version 1.17+.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ This tutorial demonstrates how to create a volume, mount a volume and use volume
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project).
|
||||
- You need to create a workspace, a project and an account (`project-regular`). The account must be invited to the project with the role of `operator`. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
- If you want to dynamically provision a volume, you need to [configure a storage class](../../../cluster-administration/persistent-volume-and-storage-class/) that supports dynamic provisioning.
|
||||
|
||||
|
|
|
|||
|
|
@ -119,7 +119,7 @@ Similar to installing KubeSphere on an existing Kubernetes cluster in an online
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can enable pluggable components in this YAML file to explore more features of KubeSphere. Refer to [Enable Pluggle Components](../../pluggable-components) for more details.
|
||||
You can enable pluggable components in this YAML file to explore more features of KubeSphere. Refer to [Enable Pluggle Components](../../pluggable-components/) for more details.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -36,4 +36,4 @@ A brand-new installer [KubeKey](https://github.com/kubesphere/kubekey) is introd
|
|||
|
||||
## KubeKey or ks-installer
|
||||
|
||||
[ks-installer](https://github.com/kubesphere/ks-installer/tree/master) was the main installation tool as of KubeSphere v2. For users whose Kubernetes clusters were NOT deployed via [KubeSphere Installer](https://v2-1.docs.kubesphere.io/docs/installation/all-in-one/#step-2-download-installer-package), they should choose ks-installer to upgrade KubeSphere. For example, if your Kubernetes is hosted by cloud vendors or self provisioned, refer to [Upgrade with ks-installer](../upgrade-with-ks-installer).
|
||||
[ks-installer](https://github.com/kubesphere/ks-installer/tree/master) was the main installation tool as of KubeSphere v2. For users whose Kubernetes clusters were NOT deployed via [KubeSphere Installer](https://v2-1.docs.kubesphere.io/docs/installation/all-in-one/#step-2-download-installer-package), they should choose ks-installer to upgrade KubeSphere. For example, if your Kubernetes is hosted by cloud vendors or self provisioned, refer to [Upgrade with ks-installer](../upgrade-with-ks-installer/).
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: "Upgrade KubeSphere with kubekey"
|
|||
linkTitle: "Upgrade with KubeKey"
|
||||
weight: 7200
|
||||
---
|
||||
KubeKey is recommended for users whose KubeSphere and Kubernetes were both deployed by the [KubeSphere Installer](https://v2-1.docs.kubesphere.io/docs/installation/all-in-one/#step-2-download-installer-package). If your Kubernetes cluster was provisioned by yourself or cloud providers, refer to [Upgrade with ks-installer](../upgrade-with-ks-installer).
|
||||
KubeKey is recommended for users whose KubeSphere and Kubernetes were both deployed by the [KubeSphere Installer](https://v2-1.docs.kubesphere.io/docs/installation/all-in-one/#step-2-download-installer-package). If your Kubernetes cluster was provisioned by yourself or cloud providers, refer to [Upgrade with ks-installer](../upgrade-with-ks-installer/).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Workspace network isolation is disabled by default. You can turn on network isol
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
When network isolation is turned on, egress traffic will be allowed by default, while ingress traffic will be denied for different workspaces. If you need to customize your network policy, you need to turn on [Project Network Isolation](../../project-administration/project-network-isolation) and add a network policy in **Project Settings**.
|
||||
When network isolation is turned on, egress traffic will be allowed by default, while ingress traffic will be denied for different workspaces. If you need to customize your network policy, you need to turn on [Project Network Isolation](../../project-administration/project-network-isolation/) and add a network policy in **Project Settings**.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -13,19 +13,19 @@ section2:
|
|||
- title: 'Recap: KubeSphere & Friends 2020 Meetup'
|
||||
description: KubeSphere and Friends 2020 Meetup attracted more than 100 individual community members and honored guests to share their ideas and experiences on cloud-native and Kubernetes.
|
||||
image: /images/news/meetup-2020/Snip20210201_8.png
|
||||
link: 'kubesphere-meetup-2020'
|
||||
link: 'kubesphere-meetup-2020/'
|
||||
- title: 'KubeSphere is Now Available as an AWS Quick Start'
|
||||
description: KubeSphere expands collaboration with Amazon Web Services to further accelerate the cloud-native technology transformation.
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/kubesphere-aws.png
|
||||
link: 'kubesphere-available-on-aws-quickstart'
|
||||
link: 'kubesphere-available-on-aws-quickstart/'
|
||||
- title: 'KubeSphere and Cigo Cloud Partner on Providing Container Services and Building a Developer Community in Africa'
|
||||
description: KubeSphere and Cigo Cloud work to empower African users on the cloud and promote a local developer community.
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/cigo-cloud.png
|
||||
link: 'kubesphere-cigo-partnership'
|
||||
link: 'kubesphere-cigo-partnership/'
|
||||
- title: 'KubeSphere 3.0.0 GA: Born for Hybrid Cloud Apps'
|
||||
description: That's a Killer! KubeSphere 3.0.0 is Now Generally Available!
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/20200830101950.png
|
||||
link: 'kubesphere-3.0.0-ga-announcement'
|
||||
link: 'kubesphere-3.0.0-ga-announcement/'
|
||||
- title: 'Bare-Metal Kubernetes Load Balancer Porter Included in CNCF Landscape'
|
||||
description: The CNCF accepted Porter, a load balancer meant for bare-metal Kubernetes clusters, in its Landscape. Porter uses BGP and ECMP to load balance traffic in self-hosted Kubernetes clusters.
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/porter-deployment.png
|
||||
|
|
@ -33,13 +33,13 @@ section2:
|
|||
- title: 'Spanish and Traditional Chinese Localization Available in KubeSphere Web Console'
|
||||
description: Geko and Turtle Chang contribute to the localization of Spanish and Traditional Chinese.
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/KubeSphere-language-setting.png
|
||||
link: 'spanish-traditional-chinese-available'
|
||||
link: 'spanish-traditional-chinese-available/'
|
||||
- title: 'Embrace KubeSphere Spanish Community and European Market: Geko and KubeSphere Build Partnership'
|
||||
description: KubeSphere and Geko will work together for the same aspiration to deliver more for the wider open source community in China, Spain and beyond.
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200725083630.png
|
||||
link: 'kubesphere-geko-partnership'
|
||||
link: 'kubesphere-geko-partnership/'
|
||||
- title: 'Radore and KubeSphere: Walk into the Future of Hybrid Cloud and Build Ecosystem Together'
|
||||
description: KubeSphere and Radore will work to build and promote both ecosystems as we embark on the journey to the era of hybrid cloud.
|
||||
image: https://ap3.qingstor.com/kubesphere-website/docs/Radore-KubeSphere-cooperation.jpeg
|
||||
link: 'kubesphere-radore-partnership'
|
||||
link: 'kubesphere-radore-partnership/'
|
||||
---
|
||||
|
|
@ -27,19 +27,19 @@ section3:
|
|||
partnerType:
|
||||
- title: "App Providers"
|
||||
content: "KubeSphere App Store is a great place to showcase your applications. KubeSphere brings your applications to tens of thousands of users, allowing them to deploy your App to Kubernetes with one click."
|
||||
link: "request"
|
||||
link: "request/"
|
||||
|
||||
- title: "Technology"
|
||||
content: Technology Partners offer hardware platforms, cloud services or applications for KubeSphere based on technical collaboration or joint solutions. If you have a solution of this kind, let's apply it to enhance user experiences.
|
||||
link: "request"
|
||||
link: "request/"
|
||||
|
||||
- title: "Cloud Providers"
|
||||
content: For any cloud providers who want to tightly integrate KubeSphere as a catalog or application in their application market for Kubernetes-based solution, do not hesitate to use KubeSphere to extend your ecosystem.
|
||||
link: "request"
|
||||
link: "request/"
|
||||
|
||||
- title: "Go-To-Market"
|
||||
content: As KubeSphere is 100% open source and free, you are able to localize KubeSphere, translate it into local languages, build local communities and develop local markets. GTM partners from around the globe work tightly with KubeSphere.
|
||||
link: "request"
|
||||
link: "request/"
|
||||
|
||||
section4:
|
||||
title: 'Featured Partners'
|
||||
|
|
|
|||
|
|
@ -15,19 +15,19 @@ list:
|
|||
- name: 'Multi-tenant Management: Creating Accounts, Roles, Workspaces, Projects and DevOps Projects'
|
||||
summary: ObjectiveIn this quickstart, as a cluster admin, you will learn how to create workspaces, roles and user accounts, and then invite new users…
|
||||
author: xxx
|
||||
link: admin-quick-start
|
||||
link: admin-quick-start/
|
||||
image:
|
||||
|
||||
- name: Managing Canary Release of Microservice Application on Kubernetes with Istio
|
||||
summary: Istio’s service mesh is able to manage traffic distribution with complete independence from deployment scaling, which enables a simpler, yet…
|
||||
author: xxx
|
||||
link: canary-release
|
||||
link: canary-release/
|
||||
image:
|
||||
|
||||
- name: Deploying a Grafana Application to Kubernetes Using Application Template
|
||||
summary: ObjectiveThis tutorial shows you how to quickly deploy a Grafana application in KubeSphere via App Template, demonstrating the basic…
|
||||
author: xxx
|
||||
link: app-template
|
||||
link: app-template/
|
||||
image:
|
||||
|
||||
- name: QCon International Software Development Conference
|
||||
|
|
@ -38,12 +38,12 @@ list:
|
|||
- name: Creating a CI/CD Pipeline to Deploy Spring Boot App to Kubernetes
|
||||
summary: ObjectiveThis tutorial shows you how to create a CI/CD Pipeline within DevOps project, which is intended for deploying a Spring Boot sample…
|
||||
author: xxx
|
||||
link: cicd-jenkinsfile
|
||||
link: cicd-jenkinsfile/
|
||||
image:
|
||||
|
||||
- name: Creating Horizontal Pod Autoscaler for Deployment
|
||||
summary: The Horizontal Pod Autoscaler automatically scales the number of pods in a deployment based on observed CPU utilization or Memory usage. The…
|
||||
author: xxx
|
||||
link: hpa
|
||||
link: hpa/
|
||||
image:
|
||||
---
|
||||
|
|
@ -14,27 +14,27 @@ section2:
|
|||
caseList:
|
||||
- icon: "images/case/case5.jpg"
|
||||
content: "安畅网络是中国市场领先的下一代云托管服务商（Cloud MSP），为客户提供云原生技术和解决方案。"
|
||||
link: "anchnet"
|
||||
link: "anchnet/"
|
||||
|
||||
- icon: "images/case/case3.jpg"
|
||||
content: "Aqara 隶属于绿米联创科技有限公司，总部位于中国，拥有 300 多家 Aqara 服务提供商和 300 多家智能家居展厅。"
|
||||
link: "aqara"
|
||||
link: "aqara/"
|
||||
|
||||
- icon: "images/case/case1.jpg"
|
||||
content: "本来生活网创办于 2012 年，是一家生鲜电商平台，提供蔬菜、水果、海鲜等优质生鲜果蔬食材食品网购服务。"
|
||||
link: "benlai"
|
||||
link: "benlai/"
|
||||
|
||||
- icon: "images/case/case2.jpg"
|
||||
content: "华夏银行股份有限公司是一家上市商业银行，于 1992 年在北京成立。"
|
||||
link: "huaxia-bank"
|
||||
link: "huaxia-bank/"
|
||||
|
||||
- icon: "images/case/maxnerva.jpg"
|
||||
content: "云智汇科技服务有限公司是富士康科技集团投资成立的子公司。"
|
||||
link: "maxnerva"
|
||||
link: "maxnerva/"
|
||||
|
||||
- icon: "images/case/vng.jpg"
|
||||
content: "通过 14 年不断的发展，VNG 已成为越南和整个东南亚地区的 IT 领导企业之一。"
|
||||
link: "vng"
|
||||
link: "vng/"
|
||||
|
||||
section3:
|
||||
title: 'KubeSphere 助力各行各业'
|
||||
|
|
|
|||
|
|
@ -13,19 +13,19 @@ list:
|
|||
- name: Porter-面向裸金属环境的 Kubernetes 开源负载均衡器
|
||||
summary: 我们知道，在 Kubernetes 集群中可以使用 “LoadBalancer” 类型的服务将后端工作负载暴露在外部。云厂商通常为 Kubernetes 提供云上的 LB 插件，但这需要将集群部署在特定 IaaS 平台上。然而，许多企业用户通常都将 Kubernetes…
|
||||
author: 宋雪涛
|
||||
link: porter
|
||||
link: porter/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200611115347.png
|
||||
|
||||
- name: 云原生可观察性之日志管理
|
||||
summary: 日志通常含有非常有价值的信息，日志管理是云原生可观察性的重要组成部分。不同于物理机或虚拟机，在容器与 Kubernetes 环境中，日志有标准的输出方式(stdout…
|
||||
author: 霍秉杰，马丹
|
||||
link: logging
|
||||
link: logging/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200607224942.png
|
||||
|
||||
- name: 基于 Kubernetes 的 Serverless Jenkins — Jenkins X
|
||||
summary: 在云原生时代，应用模块不断被拆分，使得模块的数量不断上涨并且关系也越加复杂。企业在落地云原生技术的时候同事也需要有强大的 DevOps 手段，没有 DevOps 的云原生不可能是成功的。Jenkins X 是 CDF（持续交付基金会）与
|
||||
author: 夏润泽
|
||||
link: jenkins-x
|
||||
link: jenkins-x/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20190930095450.png
|
||||
|
||||
- name: QCon 全球软件开发大会
|
||||
|
|
@ -36,6 +36,6 @@ list:
|
|||
- name: 基于 CSI Kubernetes 存储插件的开发实践
|
||||
summary: 现在很多用户都会将自己的应用迁移到 Kubernetes 容器平台中。在 Kubernetes 容器平台中，存储是支撑用户应用的基石。随着用户不断的将自己的应用深度部署在 K8S 容器平台中，但是我们现有的 Kubernetes…
|
||||
author: 王欣
|
||||
link: csi
|
||||
link: csi/
|
||||
image: https://pek3b.qingstor.com/kubesphere-docs/png/20200611114611.png
|
||||
---
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ section2:
|
|||
- content: '快速入门'
|
||||
link: '/docs/quick-start/create-workspace-and-project/'
|
||||
- content: '视频教程'
|
||||
link: '../videos'
|
||||
link: '../videos/'
|
||||
|
||||
- name: '贡献'
|
||||
icon1: 'images/contribution/contribute.svg'
|
||||
|
|
@ -274,7 +274,7 @@ section4:
|
|||
- title: '成为 Ambassador'
|
||||
icon: 'images/contribution/group-1.png'
|
||||
content: '您将会成为面向公众用户的 KubeSphere 社区代表。我们将为您提供资源，以帮助您成为一名成功的演讲者或作者。'
|
||||
link: 'request'
|
||||
link: 'request/'
|
||||
linkContent: '成为 KubeSphere Ambassador →'
|
||||
|
||||
- title: '成为 Contributor'
|
||||
|
|
|
|||
|
|
@ -15,16 +15,16 @@ sectionLink:
|
|||
title: 常用文档
|
||||
description: 通过快速入门、教程和示例等学习使用 KubeSphere。
|
||||
list:
|
||||
- /docs/quick-start/all-in-one-on-linux
|
||||
- /docs/quick-start/minimal-kubesphere-on-k8s
|
||||
- /docs/quick-start/create-workspace-and-project
|
||||
- /docs/introduction/what-is-kubesphere
|
||||
- /docs/pluggable-components
|
||||
- /docs/installing-on-linux/introduction/multioverview
|
||||
- /docs/pluggable-components/app-store
|
||||
- /docs/pluggable-components/devops
|
||||
- /docs/multicluster-management
|
||||
- /docs/project-user-guide/configuration/image-registry
|
||||
- /docs/quick-start/all-in-one-on-linux/
|
||||
- /docs/quick-start/minimal-kubesphere-on-k8s/
|
||||
- /docs/quick-start/create-workspace-and-project/
|
||||
- /docs/introduction/what-is-kubesphere/
|
||||
- /docs/pluggable-components/
|
||||
- /docs/installing-on-linux/introduction/multioverview/
|
||||
- /docs/pluggable-components/app-store/
|
||||
- /docs/pluggable-components/devops/
|
||||
- /docs/multicluster-management/
|
||||
- /docs/project-user-guide/configuration/image-registry/
|
||||
|
||||
videos:
|
||||
title: 视频教程
|
||||
|
|
|
|||
|
|
@ -41,9 +41,9 @@ Kubernetes 解决了应用编排、容器调度的难题，极大地提高了资
|
|||
|
||||
KubeSphere 中的权限控制分为平台、企业空间、项目三个层级，通过角色来控制用户在不同层级的资源访问权限。
|
||||
|
||||
1. [平台角色](../../quick-start/create-workspace-and-project)：主要控制用户对平台资源的访问权限，如集群的管理、企业空间的管理、平台用户的管理等。
|
||||
2. [企业空间角色](../../workspace-administration/role-and-member-management)：主要控制企业空间成员在企业空间下的资源访问权限，如企业空间下项目、DevOps 工程的管理等。
|
||||
3. [项目角色](../../project-administration/role-and-member-management)：主要控制项目下资源的访问权限，如工作负载的管理、流水线的管理等。
|
||||
1. [平台角色](../../quick-start/create-workspace-and-project/)：主要控制用户对平台资源的访问权限，如集群的管理、企业空间的管理、平台用户的管理等。
|
||||
2. [企业空间角色](../../workspace-administration/role-and-member-management/)：主要控制企业空间成员在企业空间下的资源访问权限，如企业空间下项目、DevOps 工程的管理等。
|
||||
3. [项目角色](../../project-administration/role-and-member-management/)：主要控制项目下资源的访问权限，如工作负载的管理、流水线的管理等。
|
||||
|
||||
### 网络隔离
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ data:
|
|||
|
||||
|
||||
|
||||
账户登录到 KubeSphere 之后就可以被添加、邀请到启用空间中[参与项目协同](https://kubesphere.io/docs/workspace-administration/role-and-member-management) 。
|
||||
账户登录到 KubeSphere 之后就可以被添加、邀请到启用空间中[参与项目协同](https://kubesphere.io/docs/workspace-administration/role-and-member-management/) 。
|
||||
|
||||
## OAuth2 插件开发
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
KubeSphere 中使用的词汇表。
|
||||
|
||||
## [KubeSphere API](../api-reference/api-docs)
|
||||
## [KubeSphere API](../api-reference/api-docs/)
|
||||
|
||||
REST API 是 KubeSphere 的基本结构。本指南向您展示如何访问 KubeSphere API 服务器。
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ KubeSphere 集成了 [OpenPitrix](https://github.com/openpitrix/openpitrix)（
|
|||
|
||||
## 准备工作
|
||||
|
||||
- 您需要启用 [KubeSphere 应用商店 (OpenPitrix)](../../pluggable-components/app-store)。
|
||||
- 您需要启用 [KubeSphere 应用商店 (OpenPitrix)](../../pluggable-components/app-store/)。
|
||||
- 您需要创建一个企业空间、一个项目以及一个帐户 (`project-regular`)。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../quick-start/create-workspace-and-project/)。
|
||||
|
||||
## 动手实验
|
||||
|
|
|
|||
|
|
@ -17,8 +17,7 @@ weight: 8300
|
|||
|
||||
1. 点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management
|
||||
)并已导入了 Member 集群，您可以选择一个集群以查看其应用程序资源。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management/)并已导入了 Member 集群，您可以选择一个集群以查看其应用程序资源。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
3. 在左侧导航栏选择**监控告警**下的**应用资源**以查看应用资源概览，包括集群中所有资源使用情况的汇总信息。
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ weight: 8622
|
|||
|
||||
1. 以 `admin` 身份登录 KubeSphere 的 Web 控制台。点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management/)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
3. 在**集群管理**页面，选择**集群设置**下的**日志收集**。
|
||||
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ EOF
|
|||
## 步骤 2：添加 Fluentd 作为日志接收器
|
||||
|
||||
1. 以 `admin` 身份登录 KubeSphere 的 Web 控制台。点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management/)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
3. 在**集群管理**页面，选择**集群设置**下的**日志收集**。
|
||||
|
||||
4. 点击**添加日志接收器**并选择 **Fluentd**。
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ weight: 8623
|
|||
|
||||
1. 以 `admin` 身份登录 KubeSphere 的 Web 控制台。点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您启用了[多集群功能](../../../../multicluster-management/)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
3. 在**集群管理**页面，选择**集群设置**下的**日志收集**。
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ KubeSphere 提供灵活的日志收集配置方式。基于 [FluentBit Operator]
|
|||
|
||||
2. 点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
|
||||
3. 如果您启用了[多集群功能](../../../../multicluster-management)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
3. 如果您启用了[多集群功能](../../../../multicluster-management/)，您可以选择一个集群。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
4. 选择**集群设置**下的**日志收集**。
|
||||
|
||||
|
|
@ -51,11 +51,11 @@ KubeSphere 提供灵活的日志收集配置方式。基于 [FluentBit Operator]
|
|||
|
||||
### 添加 Kafka 作为日志接收器
|
||||
|
||||
Kafka 往往用于接收日志，并作为 Spark 等处理系统的代理 (Broker)。[添加 Kafka 作为接收器](../add-kafka-as-receiver)演示如何添加 Kafka 接收 Kubernetes 日志。
|
||||
Kafka 往往用于接收日志，并作为 Spark 等处理系统的代理 (Broker)。[添加 Kafka 作为接收器](../add-kafka-as-receiver/)演示如何添加 Kafka 接收 Kubernetes 日志。
|
||||
|
||||
### 添加 Fluentd 作为日志接收器
|
||||
|
||||
如果您需要将日志输出到除 Elasticsearch 或 Kafka 以外的其他地方，您可以添加 Fluentd 作为日志接收器。Fluentd 支持多种输出插件，可以将日志发送至多个目标，例如 S3、MongoDB、Cassandra、MySQL、syslog 和 Splunk 等。[添加 Fluentd 作为接收器](../add-fluentd-as-receiver)演示如何添加 Fluentd 接收 Kubernetes 日志。
|
||||
如果您需要将日志输出到除 Elasticsearch 或 Kafka 以外的其他地方，您可以添加 Fluentd 作为日志接收器。Fluentd 支持多种输出插件，可以将日志发送至多个目标，例如 S3、MongoDB、Cassandra、MySQL、syslog 和 Splunk 等。[添加 Fluentd 作为接收器](../add-fluentd-as-receiver/)演示如何添加 Fluentd 接收 Kubernetes 日志。
|
||||
|
||||
## 为事件或审计日志添加日志接收器
|
||||
|
||||
|
|
|
|||
|
|
@ -18,8 +18,7 @@ KubeSphere 支持对集群 CPU、内存、网络和磁盘等资源的相关指
|
|||
|
||||
|
||||
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management
|
||||
)并已导入了 Member 集群，您可以选择一个特定集群以查看其应用程序资源。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management/)并已导入了 Member 集群，您可以选择一个特定集群以查看其应用程序资源。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -34,4 +34,4 @@ Alertmanager 可用于管理 Prometheus 以外来源发出的告警。在 3.0
|
|||
|
||||
为了使用 Alertmanager 管理平台上的告警，KubeSphere 提供了 [Notification Manager](https://github.com/kubesphere/notification-manager)，它是一个 Kubernetes 原生通知管理工具，完全开源。它符合多租户规则，提供用户友好的 Kubernetes 通知体验，3.0 版及更高版本的 KubeSphere 均默认安装 Notification Manager。
|
||||
|
||||
有关使用 Notification Manager 接收 Alertmanager 通知的详细信息，请参考 [Notification Manager](../notification-manager)。
|
||||
有关使用 Notification Manager 接收 Alertmanager 通知的详细信息，请参考 [Notification Manager](../notification-manager/)。
|
||||
|
|
@ -22,8 +22,7 @@ Kubernetes 将容器放入 Pod 中并在节点上运行，从而运行工作负
|
|||
1. 点击左上角的**平台管理**，然后选择**集群管理**。
|
||||
|
||||
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management
|
||||
)并已导入了 Member 集群，您可以选择一个特定集群以查看其节点信息。如果尚未启用该功能，请直接进行下一步。
|
||||
2. 如果您已启用了[多集群功能](../../multicluster-management/)并已导入了 Member 集群，您可以选择一个特定集群以查看其节点信息。如果尚未启用该功能，请直接进行下一步。
|
||||
|
||||
|
||||
3. 在左侧导航栏中选择**节点管理**下的**集群节点**，查看节点的状态详情。
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ weight: 11420
|
|||
- 您需要[启用多集群功能](../../../../docs/multicluster-management/)。
|
||||
- 您需要有一个 [Docker Hub](https://hub.docker.com/) 帐户。
|
||||
- 您需要[启用 KubeSphere DevOps 系统](../../../../docs/pluggable-components/devops/)。
|
||||
- 您需要创建一个多集群企业空间，在 **Host** 集群上创建一个 DevOps 工程，创建一个多集群项目（本教程中，该多集群项目创建于 Host 集群和一个 Member 集群上），并创建一个帐户 (`project-regular`)，需要邀请该帐户至 DevOps 工程和多集群项目中，并赋予 `operator` 角色。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../../quick-start/create-workspace-and-project)、[多集群管理](../../../multicluster-management)和[多集群项目](../../../project-administration/project-and-multicluster-project/#多集群项目)。
|
||||
- 您需要创建一个多集群企业空间，在 **Host** 集群上创建一个 DevOps 工程，创建一个多集群项目（本教程中，该多集群项目创建于 Host 集群和一个 Member 集群上），并创建一个帐户 (`project-regular`)，需要邀请该帐户至 DevOps 工程和多集群项目中，并赋予 `operator` 角色。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../../quick-start/create-workspace-and-project/)、[多集群管理](../../../multicluster-management/)和[多集群项目](../../../project-administration/project-and-multicluster-project/#多集群项目)。
|
||||
|
||||
## 创建 Docker Hub 访问令牌 (Token)
|
||||
|
||||
|
|
|
|||
|
|
@ -279,6 +279,6 @@ kubectl -n kubesphere-system rollout restart deploy ks-console
|
|||
|
||||
## 在 KubeSphere 控制台查看结果
|
||||
|
||||
您[使用图形编辑面板创建流水线](../../how-to-use/create-a-pipeline-using-graphical-editing-panel)或[使用 Jenkinsfile 创建流水线](../../how-to-use/create-a-pipeline-using-jenkinsfile)之后，可以查看代码质量分析的结果。如果 SonarQube 成功运行，您可能会看到下图所示结果。
|
||||
您[使用图形编辑面板创建流水线](../../how-to-use/create-a-pipeline-using-graphical-editing-panel/)或[使用 Jenkinsfile 创建流水线](../../how-to-use/create-a-pipeline-using-jenkinsfile/)之后，可以查看代码质量分析的结果。如果 SonarQube 成功运行，您可能会看到下图所示结果。
|
||||
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ Jenkinsfile 是一个文本文件，它包含 Jenkins 流水线的定义，并
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
KubeSphere 中可以创建两种类型的流水线：一种是本教程中介绍的基于 SCM 中 Jenkinsfile 创建的流水线，另一种是[通过图形编辑面板创建的流水线](../create-a-pipeline-using-graphical-editing-panel)。Jenkinsfile in SCM 需要源代码管理 (SCM) 中有内置 Jenkinsfile，换句话说，Jenkinsfile 作为 SCM 的一部分。KubeSphere DevOps 系统会根据代码仓库的现有 Jenkinsfile 自动构建 CI/CD 流水线。您可以定义工作流，例如 `stage` 和 `step`。
|
||||
KubeSphere 中可以创建两种类型的流水线：一种是本教程中介绍的基于 SCM 中 Jenkinsfile 创建的流水线，另一种是[通过图形编辑面板创建的流水线](../create-a-pipeline-using-graphical-editing-panel/)。Jenkinsfile in SCM 需要源代码管理 (SCM) 中有内置 Jenkinsfile，换句话说，Jenkinsfile 作为 SCM 的一部分。KubeSphere DevOps 系统会根据代码仓库的现有 Jenkinsfile 自动构建 CI/CD 流水线。您可以定义工作流，例如 `stage` 和 `step`。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -84,4 +84,4 @@ weight: 11230
|
|||
|
||||
[使用 Jenkinsfile 创建流水线](../create-a-pipeline-using-jenkinsfile/)
|
||||
|
||||
[使用图形编辑面板创建流水线](../create-a-pipeline-using-graphical-editing-panel)
|
||||
[使用图形编辑面板创建流水线](../create-a-pipeline-using-graphical-editing-panel/)
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Weight: 11260
|
|||
|
||||
|
||||
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management/)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。
|
||||
|
||||
3. 转到**应用负载**下的**工作负载**，然后从下拉列表中选择 **kubesphere-devops-system** 项目。点击 **ks-jenkins** 右侧的三个点以编辑其 YAML 配置文件。
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ KubeSphere DevOps 系统提供基于 Jenkins 的容器化 CI/CD 功能。为了
|
|||
|
||||
|
||||
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management)并已导入 Member 集群，您可以选择一个特定集群来编辑 ConfigMap。如果您尚未启用多集群功能，请直接参考下一步。
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management/)并已导入 Member 集群，您可以选择一个特定集群来编辑 ConfigMap。如果您尚未启用多集群功能，请直接参考下一步。
|
||||
|
||||
3. 在左侧导航栏中选择**配置中心**下的**配置**。在**配置**页面上，从下拉列表中选择 `kubesphere-devops-system`，然后点击 `jenkins-casc-config`。
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ weight: 11270
|
|||
|
||||
|
||||
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。
|
||||
2. 如果您已经启用[多集群功能](../../../multicluster-management/)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。
|
||||
|
||||
3. 转到**节点管理**下的**集群节点**，您可以在其中查看当前集群中的现有节点。
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ KubeSphere 为用户提供轻量级安装程序 [KubeKey](https://github.com/kub
|
|||
- 对于 All-in-One，唯一的节点既是主节点，也是工作节点。
|
||||
- 对于多节点安装，需要在配置文件中提供主机信息。
|
||||
- Linux 主机必须已安装 OpenSSH Server。
|
||||
- 在安装之前，请参见[端口要求](../port-firewall)。
|
||||
- 在安装之前，请参见[端口要求](../port-firewall/)。
|
||||
|
||||
## KubeKey
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ KubeSphere 为用户提供轻量级安装程序 [KubeKey](https://github.com/kub
|
|||
|
||||
### 删除节点
|
||||
|
||||
您需要清空节点负载，然后再删除节点。有关更多信息，请参见[删除节点](../../cluster-operation/remove-nodes)。
|
||||
您需要清空节点负载，然后再删除节点。有关更多信息，请参见[删除节点](../../cluster-operation/remove-nodes/)。
|
||||
|
||||
## 卸载
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ weight: 3340
|
|||
|
||||
## 步骤 3：下载 KubeKey
|
||||
|
||||
根据以下步骤在任务机上下载 [KubeKey](../../../installing-on-linux/introduction/kubekey)。
|
||||
根据以下步骤在任务机上下载 [KubeKey](../../../installing-on-linux/introduction/kubekey/)。
|
||||
|
||||
{{< tabs >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ weight: 1500
|
|||
|
||||
## 前后端分离
|
||||
|
||||
KubeSphere 将 [前端](https://github.com/kubesphere/console) 与 [后端](https://github.com/kubesphere/kubesphere) 分开，实现了面向云原生的设计，后端的各个功能组件可通过 REST API 对接外部系统。 可参考 [API文档](../../api-reference/api-docs)。下图是系统架构图。 KubeSphere 无底层的基础设施依赖，可以运行在任何 Kubernetes、私有云、公有云、VM 或物理环境（BM）之上。 此外，它可以部署在任何 Kubernetes 发行版上。
|
||||
KubeSphere 将 [前端](https://github.com/kubesphere/console) 与 [后端](https://github.com/kubesphere/kubesphere) 分开，实现了面向云原生的设计，后端的各个功能组件可通过 REST API 对接外部系统。 可参考 [API文档](../../api-reference/api-docs/)。下图是系统架构图。 KubeSphere 无底层的基础设施依赖，可以运行在任何 Kubernetes、私有云、公有云、VM 或物理环境（BM）之上。 此外，它可以部署在任何 Kubernetes 发行版上。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ KubeSphere 可以在不修改用户当前的资源或资产、不影响其业务
|
|||
|
||||
## 完全开源
|
||||
|
||||
借助开源的模式，KubeSphere 社区驱动着开发工作以开放的方式进行。KubeSphere **100% 开源免费**，已大规模服务于社区用户，广泛地应用在以 Docker 和 Kubernetes 为中心的开发、测试及生产环境中，大量服务平稳地运行在 KubeSphere 之上。您可在 [GitHub](https://github.com/kubesphere/) 上找到所有源代码、文档和讨论，所有主要的开源项目介绍可以在[开源项目列表](../../../projects)中找到。
|
||||
借助开源的模式，KubeSphere 社区驱动着开发工作以开放的方式进行。KubeSphere **100% 开源免费**，已大规模服务于社区用户，广泛地应用在以 Docker 和 Kubernetes 为中心的开发、测试及生产环境中，大量服务平稳地运行在 KubeSphere 之上。您可在 [GitHub](https://github.com/kubesphere/) 上找到所有源代码、文档和讨论，所有主要的开源项目介绍可以在[开源项目列表](../../../projects/)中找到。
|
||||
|
||||
## 云原生 Landscape
|
||||
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@ description: '导入 AWS EKS 集群'
|
|||
weight: 5320
|
||||
---
|
||||
|
||||
在本节中，我们将向您展示如何使用[直接连接](../../enable-multicluster/direct-connection)方法将 EKS 导入 KubeSphere。
|
||||
在本节中，我们将向您展示如何使用[直接连接](../../enable-multicluster/direct-connection/)方法将 EKS 导入 KubeSphere。
|
||||
|
||||
{{< notice note >}}
|
||||
如果您打算使用[代理连接](../../enable-multicluster/agent-connection)导入 EKS，则可以跳过本章节并按照[代理连接](../../enable-multicluster/agent-connection)的文档逐步进行。
|
||||
如果您打算使用[代理连接](../../enable-multicluster/agent-connection/)导入 EKS，则可以跳过本章节并按照[代理连接](../../enable-multicluster/agent-connection/)的文档逐步进行。
|
||||
{{</ notice >}}
|
||||
|
||||
[Amazon EKS](https://docs.aws.amazon.com/eks/index.html)不像标准 kubeadm 集群那样提供内置的 kubeconfig 文件。但是您可以通过参考此[文档](https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html)自动创建 kubeconfig。生成的 kubeconfig 将如下所示，
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 6500
|
|||
|
||||
KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如节点调度状态和镜像拉取结果。这些事件会被准确记录下来，并在 Web 控制台中显示具体的原因、状态和信息。要查询事件，用户可以快速启动 Web 工具箱，在搜索栏中输入相关信息，并有不同的过滤器（如关键字和项目）可供选择。事件也可以归档到第三方工具，例如 Elasticsearch、Kafka 或 Fluentd。
|
||||
|
||||
有关更多信息，请参见[事件查询](../../toolbox/events-query)。
|
||||
有关更多信息，请参见[事件查询](../../toolbox/events-query/)。
|
||||
|
||||
## 在安装前启用事件系统
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ KubeSphere 支持多种日志收集方式，使运维团队能够以灵活统一
|
|||
|
||||
## 准备工作
|
||||
|
||||
- 您需要创建企业空间、项目和帐户 (`project-admin`)。该帐户必须被邀请到项目中，并在项目级别具有 `admin` 角色。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../quick-start/create-workspace-and-project)。
|
||||
- 您需要创建企业空间、项目和帐户 (`project-admin`)。该帐户必须被邀请到项目中，并在项目级别具有 `admin` 角色。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../quick-start/create-workspace-and-project/)。
|
||||
|
||||
- 您需要启用 [KubeSphere 日志系统](../../pluggable-components/logging/)。
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ KubeSphere 项目中的网关是一个[ NGINX Ingress 控制器](https://www.ngi
|
|||
|
||||
## 准备工作
|
||||
|
||||
您需要创建一个企业空间、一个项目和一个帐户 (`project-admin`)。该帐户必须被邀请至项目，并且在项目中的角色为 `admin`。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../../docs/quick-start/create-workspace-and-project)。
|
||||
您需要创建一个企业空间、一个项目和一个帐户 (`project-admin`)。该帐户必须被邀请至项目，并且在项目中的角色为 `admin`。有关更多信息，请参见[创建企业空间、项目、帐户和角色](../../../docs/quick-start/create-workspace-and-project/)。
|
||||
|
||||
## 设置网关
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ weight: 10720
|
|||
## 准备工作
|
||||
|
||||
* 您需要启用 [KubeSphere 告警和通知](../../../pluggable-components/alerting-notification/)。
|
||||
* 您需要创建一个企业空间、一个项目和一个帐户（例如 `project-regular`）。该帐户必须已邀请至该项目，并具有 `operator` 角色。有关更多信息，请参阅[创建企业空间、项目、帐户和角色](../../../quick-start/create-workspace-and-project)。
|
||||
* 您需要创建一个企业空间、一个项目和一个帐户（例如 `project-regular`）。该帐户必须已邀请至该项目，并具有 `operator` 角色。有关更多信息，请参阅[创建企业空间、项目、帐户和角色](../../../quick-start/create-workspace-and-project/)。
|
||||
* 您需要创建一个工作负载级别的告警策略并接收到相关告警通知。如果尚未创建告警策略，请按照[告警策略（工作负载级别）](../alerting-policy/)创建一个告警策略。
|
||||
|
||||
## 动手实验
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue