mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Update 3.2.0 docs
Signed-off-by: serenashe <serenashe@kubesphere.io>
This commit is contained in:
serenashe
parent
877c3b0b90
commit
dc5e28981c
|
|
@ -5,6 +5,6 @@ _build:
|
|||
|
||||
| Installation Tool | KubeSphere version | Supported Kubernetes versions |
|
||||
| ----------------- | ------------------ | ------------------------------------------------------------ |
|
||||
| KubeKey | v3.2.0 | v1.19.0, v1.19.8, v1.19.9, v1.20.4, v1.20.6, v1.21.5, v1.22.1 |
|
||||
| ks-installer | v3.2.0 | v1.19.x, v1.20.x, v1.21.5, v1.22.1 |
|
||||
| KubeKey | 3.2.0 | v1.19.x, v1.20.x, v1.21.x, v1.22.x (experimental) |
|
||||
| ks-installer | 3.2.0 | v1.19.x, v1.20.x, v1.21.x, v1.22.x (experimental) |
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "Cluster Gateway"
|
|||
weight: 8630
|
||||
---
|
||||
|
||||
KubeSphere v3.2.0 provides cluster-scope gateways to let all projects share a global project gateway. This document describes how to set a cluster gateway on KubeSphere.
|
||||
KubeSphere 3.2.0 provides cluster-scope gateways to let all projects share a global project gateway. This document describes how to set a cluster gateway on KubeSphere.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ KubeSphere monitors the health status of various service components in the clust
|
|||
|
||||
## Physical Resource Monitoring
|
||||
|
||||
Monitoring data in **Physical Resource Monitoring** help users better observe their physical resources and establish normal standards for resource and cluster performance. KubeSphere allows users to view cluster monitoring data within the last 7 days, including **CPU Usage**, **Memory Usage**, **Average CPU Load (1 minute/5 minutes/15 minutes)**, **Inode Usage**, **Disk Throughput (read/write)**, **IOPS (read/write)**, **Network Bandwidth**, and **Pod Status**. You can customize the time range and time interval to view historical monitoring data of physical resources in KubeSphere. The following sections briefly introduce each monitoring indicator.
|
||||
Monitoring data in **Physical Resource Monitoring** help users better observe their physical resources and establish normal standards for resource and cluster performance. KubeSphere allows users to view cluster monitoring data within the last 7 days, including **CPU Usage**, **Memory Usage**, **Average CPU Load (1 minute/5 minutes/15 minutes)**, **Disk Usage**, **Inode Usage**, **Disk Throughput (read/write)**, **IOPS (read/write)**, **Network Bandwidth**, and **Pod Status**. You can customize the time range and time interval to view historical monitoring data of physical resources in KubeSphere. The following sections briefly introduce each monitoring indicator.
|
||||
|
||||
### CPU usage
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ To edit an alerting policy after it is created, on the **Alerting Policies** pag
|
|||
|
||||
## View an Alerting Policy
|
||||
|
||||
Click the name of an alerting policy on the **Alerting Policies** page to see its detail information, including the alerting rule and alerting messages. You can also see the rule expression which is based on the template you use when creating the alerting policy.
|
||||
Click the name of an alerting policy on the **Alerting Policies** page to see its detail information, including the alerting rule and alerting history. You can also see the rule expression which is based on the template you use when creating the alerting policy.
|
||||
|
||||
Under **Monitoring**, the **Alert Monitoring** chart shows the actual usage or amount of resources over time. **Alerting Message** displays the customized message you set in notifications.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "Persistent Volumes and Storage Classes"
|
|||
weight: 8400
|
||||
---
|
||||
|
||||
This tutorial describes the basic concepts of PVs, PVCs and storage classes and demonstrates how a cluster administrator can manage storage classes and persistent volumes in KubeSphere.
|
||||
This tutorial describes the basic concepts of PVs, PVCs, and storage classes and demonstrates how a cluster administrator can manage storage classes and persistent volumes in KubeSphere.
|
||||
|
||||
## Introduction
|
||||
|
||||
|
|
|
|||
|
|
@ -28,6 +28,6 @@ kubectl patch users <USERNAME> -p '{"spec":{"password":"<YOURPASSWORD>"}}' --typ
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
Make sure you replace `<USERNAME>` and `<YOURPASSWORD>` with the account and the new password in the command before you run it.
|
||||
Make sure you replace `<USERNAME>` and `<YOURPASSWORD>` with the username and the new password in the command before you run it.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -6,7 +6,7 @@ linkTitle: "Remove Built-in Apps in KubeSphere"
|
|||
Weight: 16910
|
||||
---
|
||||
|
||||
As an open source and app-centric container platform, KubeSphere integrates 17 built-in apps in the App Store that is based on [OpenPitrix](https://github.com/openpitrix/openpitrix). They are accessible to all tenants in a workspace, while you can also remove them from the App Store. This tutorial demonstrates how to remove a built-in app from the App Store.
|
||||
As an open source and app-centric container platform, KubeSphere integrates apps in the App Store that is based on [OpenPitrix](https://github.com/openpitrix/openpitrix). They are accessible to all tenants in a workspace, while you can also remove them from the App Store. This tutorial demonstrates how to remove a built-in app from the App Store.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
@ -17,7 +17,7 @@ As an open source and app-centric container platform, KubeSphere integrates 17 b
|
|||
|
||||
1. Log in to the web console of KubeSphere as `admin`, click **Platform** in the upper-left corner, and then select **App Store Management**.
|
||||
|
||||
2. On the **App Store** page, you can see all 17 built-in apps in the list. Select an app that you want to remove from the App Store. For example, click **Tomcat** to go to its detail page.
|
||||
2. On the **Apps** page, you can see all apps in the list. Select an app that you want to remove from the App Store. For example, click **Tomcat** to go to its detail page.
|
||||
|
||||
3. On the detail page of Tomcat, click **Suspend App** to remove the app.
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `alerting` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@ linkTitle: "KubeSphere App Store"
|
|||
weight: 6200
|
||||
---
|
||||
|
||||
As an open-source and app-centric container platform, KubeSphere provides users with a Helm-based App Store for application lifecycle management on the back of [OpenPitrix](https://github.com/openpitrix/openpitrix), an open-source web-based system to package, deploy and manage different types of apps. The KubeSphere App Store allows ISVs, developers and users to upload, test, deploy and release apps with just several clicks in a one-stop shop.
|
||||
As an open-source and app-centric container platform, KubeSphere provides users with a Helm-based App Store for application lifecycle management on the back of [OpenPitrix](https://github.com/openpitrix/openpitrix), an open-source web-based system to package, deploy and manage different types of apps. The KubeSphere App Store allows ISVs, developers, and users to upload, test, install, and release apps with just several clicks in a one-stop shop.
|
||||
|
||||
Internally, the KubeSphere App Store can serve as a place for different teams to share data, middleware, and office applications. Externally, it is conducive to setting industry standards of building and delivery. By default, there are 17 built-in apps in the App Store. After you enable this feature, you can add more apps with app templates.
|
||||
Internally, the KubeSphere App Store can serve as a place for different teams to share data, middleware, and office applications. Externally, it is conducive to setting industry standards of building and delivery. After you enable this feature, you can add more apps with app templates.
|
||||
|
||||
For more information, see [App Store](../../application-store/).
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `openpitrix` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
@ -104,12 +104,12 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
## Verify the Installation of the Component
|
||||
|
||||
After you log in to the console, if you can see **App Store** in the upper-left corner and 17 built-in apps in it, it means the installation is successful.
|
||||
After you log in to the console, if you can see **App Store** in the upper-left corner and apps in it, it means the installation is successful.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
- You can even access the App Store without logging in to the console by visiting `<Node IP Address>:30880/apps`.
|
||||
- The **OpenPitrix** tab in KubeSphere 3.2 does not appear on the **System Components** page after the App Store is enabled.
|
||||
- The **OpenPitrix** tab in KubeSphere 3.2.0 does not appear on the **System Components** page after the App Store is enabled.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: "KubeSphere Auditing Logs"
|
||||
title: "KubeSphere Audit Logs"
|
||||
keywords: "Kubernetes, auditing, KubeSphere, logs"
|
||||
description: "Learn how to enable Auditing to document platform events and activities."
|
||||
linkTitle: "KubeSphere Auditing Logs"
|
||||
linkTitle: "KubeSphere Audit Logs"
|
||||
weight: 6700
|
||||
---
|
||||
|
||||
|
|
@ -106,7 +106,7 @@ By default, ks-installer will install Elasticsearch internally if Auditing is en
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `auditing` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
@ -148,7 +148,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
{{< tab "Verify the component on the dashboard" >}}
|
||||
|
||||
Verify that you can use the **Auditing Operating** function from the **Toolbox** in the lower-right corner.
|
||||
Verify that you can use the **Audit Log Search** function from the **Toolbox** in the lower-right corner.
|
||||
|
||||
{{</ tab >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `devops` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `events` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
@ -154,7 +154,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
{{< tab "Verify the component on the dashboard" >}}
|
||||
|
||||
Verify that you can use the **Event Search** function from the **Toolbox** in the lower-right corner.
|
||||
Verify that you can use the **Resource Event Search** function from the **Toolbox** in the lower-right corner.
|
||||
|
||||
{{</ tab >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubeedge/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubeedge/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `kubeedge.enabled` and enable it by setting it to `true`.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "KubeSphere Logging System"
|
|||
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.
|
||||
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/).
|
||||
|
||||
|
|
@ -112,7 +112,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `logging` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ If you install KubeSphere on some cloud hosted Kubernetes engines, it is probabl
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/metrics-server/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/metrics-server/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `metrics_server` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `network.networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ The request and limit of CPU and memory resources all refer to single replica.
|
|||
| Namespace | kubesphere-devops-system | kubesphere-devops-system |
|
||||
| -------------- | ------------------------------------------------------------ | ------------------------------------------------------- |
|
||||
| Pattern | All-in-One installation | Multi-node installation |
|
||||
| CPU Request | 34 m | 0.47 core |
|
||||
| CPU Request | 34 m | 0.47 core心 |
|
||||
| CPU Limit | | |
|
||||
| Memory Request | 2.69 G | 8.6 G |
|
||||
| Memory Limit | | |
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `network` and change `network.ippool.type` to `calico`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "KubeSphere Service Mesh"
|
|||
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.
|
||||
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, 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/).
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `servicemesh` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/service-topology/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click <img src="/images/docs/enable-pluggable-components/service-topology/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, navigate to `network` and change `network.topology.type` to `weave-scope`. After you finish, click **OK** in the lower-right corner to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: "Uninstall Pluggable Components from KubeSphere v3.2.0"
|
||||
title: "Uninstall Pluggable Components from KubeSphere 3.2.0"
|
||||
keywords: "Installer, uninstall, KubeSphere, Kubernetes"
|
||||
description: "Learn how to uninstall each pluggable component in KubeSphere v3.2.0."
|
||||
linkTitle: "Uninstall Pluggable Components from KubeSphere v3.2.0"
|
||||
description: "Learn how to uninstall each pluggable component in KubeSphere 3.2.0."
|
||||
linkTitle: "Uninstall Pluggable Components from KubeSphere 3.2.0"
|
||||
Weight: 6940
|
||||
---
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ After you [enable the pluggable components of KubeSphere](../../pluggable-compon
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
The methods of uninstalling certain pluggable components on KubeSphere v3.2.0 are different from the methods on KubeSphere v3.0.0. For more information about the uninstallation methods on KubeSphere v3.0.0, see [Uninstall Pluggable Components from KubeSphere](https://v3-0.docs.kubesphere.io/docs/faq/installation/uninstall-pluggable-components/).
|
||||
The methods of uninstalling certain pluggable components on KubeSphere 3.2.0 are different from the methods on KubeSphere v3.0.0. For more information about the uninstallation methods on KubeSphere v3.0.0, see [Uninstall Pluggable Components from KubeSphere](https://v3-0.docs.kubesphere.io/docs/faq/installation/uninstall-pluggable-components/).
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -146,7 +146,7 @@ Change the value of `openpitrix.store.enabled` from `true` to `false` in `ks-ins
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
Notification is installed in KubeSphere v3.2.0 by default, so you do not need to uninstall it.
|
||||
Notification is installed in KubeSphere 3.2.0 by default, so you do not need to uninstall it.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ If you need to enable [KubeEdge](../../pluggable-components/kubeedge/), [Pod IP
|
|||
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
|
||||
{{</ notice >}}
|
||||
|
||||
3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**.
|
||||
3. In **Custom Resources**, click the three dots on the right of `ks-installer` and select **Edit YAML**.
|
||||
|
||||
4. In this YAML file, enable the pluggable components you want to install by changing `false` to `true` for `enabled`. After you finish, click **Update** to save the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ You need to enable [KubeSphere Auditing Logs](../../../pluggable-components/audi
|
|||
|
||||
## Enter the Query Interface
|
||||
|
||||
1. The query function is available for all users. Log in to the console with any user, hover over the <img src="/images/docs/toolbox/auditing-query/toolbox.png" width="20" /> in the lower-right corner and select **Auditing Operating**.
|
||||
1. The query function is available for all users. Log in to the console with any user, hover over the <img src="/images/docs/toolbox/auditing-query/toolbox.png" width="20" /> in the lower-right corner and select **Audit Log Search**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -28,7 +28,7 @@ Any user has the permission to query auditing logs, while the logs that each use
|
|||
|
||||
2. In the pop-up window, you can view log trends in the last 12 hours.
|
||||
|
||||
3. The **Auditing Operating** console supports the following query parameters:
|
||||
3. The **Audit Log Search** console supports the following query parameters:
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ This guide demonstrates how you can do multi-level, fine-grained event queries t
|
|||
|
||||
## Query Events
|
||||
|
||||
1. The event query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/toolbox/event-query/toolbox.png" width='20' /> in the lower-right corner and select **Event Search**.
|
||||
1. The event query function is available for all users. Log in to the console with any account, hover over <img src="/images/docs/toolbox/event-query/toolbox.png" width='20' /> in the lower-right corner and select **Resource Event Search**.
|
||||
|
||||
2. In the displayed dialog box, you can view the number of events that the user has permission to view.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,4 +11,4 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
---
|
||||
|
||||
This chapter demonstrates how cluster operators can upgrade KubeSphere to v3.2.0.
|
||||
This chapter demonstrates how cluster operators can upgrade KubeSphere to 3.2.0.
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Air-Gapped Upgrade with ks-installer"
|
||||
keywords: "Air-Gapped, upgrade, kubesphere, v3.2.0"
|
||||
keywords: "Air-Gapped, upgrade, kubesphere, 3.2.0"
|
||||
description: "Use ks-installer and offline package to upgrade KubeSphere."
|
||||
linkTitle: "Air-Gapped Upgrade with ks-installer"
|
||||
weight: 7500
|
||||
|
|
@ -15,7 +15,7 @@ ks-installer is recommended for users whose Kubernetes clusters were not set up
|
|||
- Read [Release Notes for 3.2.0](../../release/release-v320/) carefully.
|
||||
- Back up any important component beforehand.
|
||||
- A Docker registry. You need to have a Harbor or other Docker registries. For more information, see [Prepare a Private Image Registry](../../installing-on-linux/introduction/air-gapped-installation/#step-2-prepare-a-private-image-registry).
|
||||
- Supported Kubernetes versions of KubeSphere v3.2.0: v1.19.x, v1.20.x, v1.21.5, and v1.22.1.
|
||||
- Supported Kubernetes versions of KubeSphere 3.2.0: v1.19.x, v1.20.x, v1.21.x, and v1.22.x (experimental).
|
||||
|
||||
## Step 1: Prepare Installation Images
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Air-Gapped Upgrade with KubeKey"
|
||||
keywords: "Air-Gapped, kubernetes, upgrade, kubesphere, v3.2.0"
|
||||
keywords: "Air-Gapped, kubernetes, upgrade, kubesphere, 3.2.0"
|
||||
description: "Use the offline package to upgrade Kubernetes and KubeSphere."
|
||||
linkTitle: "Air-Gapped Upgrade with KubeKey"
|
||||
weight: 7400
|
||||
|
|
@ -47,7 +47,7 @@ KubeKey upgrades Kubernetes from one MINOR version to the next MINOR version unt
|
|||
|
||||
### Step 1: Download KubeKey
|
||||
|
||||
Similar to installing KubeSphere on Linux in an online environment, you need to [download KubeKey v1.1.0](https://github.com/kubesphere/kubekey/releases) first. Download the `tar.gz` file, and transfer it to your local machine which serves as the taskbox for installation. After you uncompress the file, execute the following command to make `kk` executable:
|
||||
Similar to installing KubeSphere on Linux in an online environment, you need to [download KubeKey v1.2.0](https://github.com/kubesphere/kubekey/releases) first. Download the `tar.gz` file, and transfer it to your local machine which serves as the taskbox for installation. After you uncompress the file, execute the following command to make `kk` executable:
|
||||
|
||||
```bash
|
||||
chmod +x kk
|
||||
|
|
@ -113,7 +113,7 @@ As you install KubeSphere and Kubernetes on Linux, you need to prepare an image
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
- You can change the Kubernetes version downloaded based on your needs. Recommended Kubernetes versions for KubeSphere v3.2.0 are v1.19.x, v1.20.x, v1.21.x, and v1.22.x (experimental). If you do not specify a Kubernetes version, KubeKey will install Kubernetes v1.21.5 by default. For more information about supported Kubernetes versions, see [Support Matrix](../../installing-on-linux/introduction/kubekey/#support-matrix).
|
||||
- You can change the Kubernetes version downloaded based on your needs. Recommended Kubernetes versions for KubeSphere 3.2.0 are v1.19.x, v1.20.x, v1.21.x, and v1.22.x (experimental). If you do not specify a Kubernetes version, KubeKey will install Kubernetes v1.21.5 by default. For more information about supported Kubernetes versions, see [Support Matrix](../../installing-on-linux/introduction/kubekey/#support-matrix).
|
||||
|
||||
- You can upgrade Kubernetes from v1.16.13 to v1.17.9 by downloading the v1.17.9 Kubernetes binary file, but for cross-version upgrades, all intermediate versions need to be downloaded in advance. For example, if you want to upgrade Kubernetes from v1.15.12 to v1.18.6, you need to download Kubernetes v1.16.13 and v1.17.9, and the v1.18.6 binary file.
|
||||
|
||||
|
|
@ -160,7 +160,7 @@ Transfer your packaged image file to your local machine and execute the followin
|
|||
| | Kubernetes | KubeSphere |
|
||||
| ------ | ---------- | ---------- |
|
||||
| Before | v1.18.6 | v3.1.x |
|
||||
| After | v1.21.5 | v3.2.0 |
|
||||
| After | v1.21.5 | 3.2.0 |
|
||||
|
||||
#### Upgrade a cluster
|
||||
|
||||
|
|
@ -218,7 +218,7 @@ Set `privateRegistry` of your `config-sample.yaml` file:
|
|||
privateRegistry: dockerhub.kubekey.local
|
||||
```
|
||||
|
||||
#### Upgrade your single-node cluster to KubeSphere v3.2.0 and Kubernetes v1.21.5
|
||||
#### Upgrade your single-node cluster to KubeSphere 3.2.0 and Kubernetes v1.21.5
|
||||
|
||||
```bash
|
||||
./kk upgrade -f config-sample.yaml
|
||||
|
|
@ -248,7 +248,7 @@ To upgrade Kubernetes to a specific version, explicitly provide the version afte
|
|||
| | Kubernetes | KubeSphere |
|
||||
| ------ | ---------- | ---------- |
|
||||
| Before | v1.18.6 | v3.1.x |
|
||||
| After | v1.21.5 | v3.2.0 |
|
||||
| After | v1.21.5 | 3.2.0 |
|
||||
|
||||
#### Upgrade a cluster
|
||||
|
||||
|
|
@ -308,7 +308,7 @@ Set `privateRegistry` of your `config-sample.yaml` file:
|
|||
privateRegistry: dockerhub.kubekey.local
|
||||
```
|
||||
|
||||
#### Upgrade your multi-node cluster to KubeSphere v3.2.0 and Kubernetes v1.21.5
|
||||
#### Upgrade your multi-node cluster to KubeSphere 3.2.0 and Kubernetes v1.21.5
|
||||
|
||||
```bash
|
||||
./kk upgrade -f config-sample.yaml
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Upgrade — Overview"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, v3.2.0, upgrade"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, 3.2.0, upgrade"
|
||||
description: "Understand what you need to pay attention to before the upgrade, such as versions, and upgrade tools."
|
||||
linkTitle: "Overview"
|
||||
weight: 7100
|
||||
|
|
@ -8,10 +8,10 @@ weight: 7100
|
|||
|
||||
## Make Your Upgrade Plan
|
||||
|
||||
KubeSphere v3.2.0 is compatible with Kubernetes 1.19.x, 1.20.x, 1.21.5, and 1.22.1:
|
||||
KubeSphere 3.2.0 is compatible with Kubernetes 1.19.x, 1.20.x, 1.21.x, and 1.22.x (experimental):
|
||||
|
||||
- Before you upgrade your cluster to KubeSphere v3.2.0, you need to have a KubeSphere cluster running v3.1.x.
|
||||
- If your existing KubeSphere v3.1.x cluster is installed on Kubernetes 1.19.x+, you can choose to only upgrade KubeSphere to v3.2.0 or upgrade Kubernetes (to a higher version) and KubeSphere (to v3.2.0) at the same time.
|
||||
- Before you upgrade your cluster to KubeSphere 3.2.0, you need to have a KubeSphere cluster running v3.1.x.
|
||||
- If your existing KubeSphere v3.1.x cluster is installed on Kubernetes 1.19.x+, you can choose to only upgrade KubeSphere to 3.2.0 or upgrade Kubernetes (to a higher version) and KubeSphere (to 3.2.0) at the same time.
|
||||
|
||||
## Before the Upgrade
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ ks-installer is recommended for users whose Kubernetes clusters were not set up
|
|||
- You need to have a KubeSphere cluster running v3.1.x. If your KubeSphere version is v3.0.0 or earlier, upgrade to v3.1.x first.
|
||||
- Read [Release Notes for 3.2.0](../../release/release-v320/) carefully.
|
||||
- Back up any important component beforehand.
|
||||
- Supported Kubernetes versions of KubeSphere v3.2.0: v1.19.x, v1.20.x, v1.21.5, and v1.22.1.
|
||||
- Supported Kubernetes versions of KubeSphere v3.2.0: v1.19.x, v1.20.x, v1.21.x, and v1.22.x (experimental).
|
||||
|
||||
## Apply ks-installer
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Upgrade with KubeKey"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, v3.2.0, KubeKey"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, 3.2.0, KubeKey"
|
||||
description: "Use KubeKey to upgrade Kubernetes and KubeSphere."
|
||||
linkTitle: "Upgrade with KubeKey"
|
||||
weight: 7200
|
||||
|
|
@ -80,7 +80,7 @@ When upgrading Kubernetes, KubeKey will upgrade from one MINOR version to the ne
|
|||
|
||||
### All-in-one cluster
|
||||
|
||||
Run the following command to use KubeKey to upgrade your single-node cluster to KubeSphere v3.2.0 and Kubernetes v1.21.5:
|
||||
Run the following command to use KubeKey to upgrade your single-node cluster to KubeSphere 3.2.0 and Kubernetes v1.21.5:
|
||||
|
||||
```bash
|
||||
./kk upgrade --with-kubernetes v1.21.5 --with-kubesphere v3.2.0
|
||||
|
|
@ -125,7 +125,7 @@ For more information, see [Edit the configuration file](../../installing-on-linu
|
|||
{{</ notice >}}
|
||||
|
||||
#### Step 3: Upgrade your cluster
|
||||
The following command upgrades your cluster to KubeSphere v3.2.0 and Kubernetes v1.21.5:
|
||||
The following command upgrades your cluster to KubeSphere 3.2.0 and Kubernetes v1.21.5:
|
||||
|
||||
```bash
|
||||
./kk upgrade --with-kubernetes v1.21.5 --with-kubesphere v3.2.0 -f sample.yaml
|
||||
|
|
@ -140,6 +140,6 @@ To upgrade Kubernetes to a specific version, explicitly provide the version afte
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
To use new features of KubeSphere v3.2.0, you may need to enable some pluggable components after the upgrade.
|
||||
To use new features of KubeSphere 3.2.0, you may need to enable some pluggable components after the upgrade.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "Changes after Upgrade"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, v3.2.0"
|
||||
keywords: "Kubernetes, upgrade, KubeSphere, 3.2.0"
|
||||
description: "Understand what will be changed after the upgrade."
|
||||
|
||||
linkTitle: "Changes after Upgrade"
|
||||
|
|
|
|||
|
|
@ -31,8 +31,8 @@ Maximum accepted resolutions of the app icon: 96 x 96 pixels.
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
5. The app appears in the template list with the status **Draft** after successfully uploaded, which means this app is under development. The uploaded app is visible to all members in the same workspace.
|
||||
5. The app appears in the template list with the status **Developing** after successfully uploaded, which means this app is under development. The uploaded app is visible to all members in the same workspace.
|
||||
|
||||
6. Click the app and the page opens with the **Versions** tab selected. Click the draft version to expand the menu, where you can see options including **Delete**, **Test Installation**, and **Submit for Review**.
|
||||
6. Click the app and the page opens with the **Versions** tab selected. Click the draft version to expand the menu, where you can see options including **Delete**, **Install**, and **Submit for Release**.
|
||||
|
||||
7. For more information about how to release your app to the App Store, refer to [Application Lifecycle Management](../../application-store/app-lifecycle-management/#step-2-upload-and-submit-application).
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ You have an available workspace and a user (`ws-manager`). The user must have th
|
|||
|
||||
2. Navigate to **Workspace Quotas** under **Workspace Settings**.
|
||||
|
||||
3. The **Workspace Quotas** page lists all the available clusters assigned to the workspace and their respective requests and limits of CPU and memory. Click **Edit Workspace Quotas** on the right of a cluster.
|
||||
3. The **Workspace Quotas** page lists all the available clusters assigned to the workspace and their respective requests and limits of CPU and memory. Click **Edit Quotas** on the right of a cluster.
|
||||
|
||||
4. In the displayed dialog box, you can see that KubeSphere does not set any requests or limits for the workspace by default. To set requests and limits to control CPU and memory resources, move <img src="/images/docs/common-icons/slider.png" width="20" /> to a desired value or enter numbers directly. Leaving a field blank means you do not set any requests or limits.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,5 +5,5 @@ _build:
|
|||
|
||||
| 安装工具 | KubeSphere 版本 | 支持的 Kubernetes 版本 |
|
||||
| ------------ | --------------- | ------------------------------------------------------------ |
|
||||
| KubeKey | v3.2.0 | v1.19.0, v1.19.8, v1.19.9, v1.20.4, v1.20.6, v1.21.5, v1.22.1 |
|
||||
| ks-installer | v3.2.0 | v1.19.x, v1.20.x, v1.21.5, v1.22.1 |
|
||||
| KubeKey | 3.2.0 | v1.19.x, v1.20.x, v1.21.x, v1.22.x（实验性支持） |
|
||||
| ks-installer | 3.2.0 | v1.19.x, v1.20.x, v1.21.x, v1.22.x（实验性支持） |
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "Cluster Gateway"
|
|||
weight: 8630
|
||||
---
|
||||
|
||||
KubeSphere v3.2.0 provides cluster-scope gateways to let all projects share a global project gateway. This document describes how to set a cluster gateway on KubeSphere.
|
||||
KubeSphere 3.2.0 provides cluster-scope gateways to let all projects share a global project gateway. This document describes how to set a cluster gateway on KubeSphere.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ KubeSphere 监控集群中各种服务组件的健康状态。当关键组件发
|
|||
|
||||
## 物理资源监控
|
||||
|
||||
您可以利用**物理资源监控**页面提供的数据更好地掌控物理资源状态，并建立正常资源和集群性能的标准。KubeSphere 允许用户查看最近 7 天的集群监控数据，包括 **CPU 用量**、**内存用量**、**CPU 平均负载（1 分钟/5 分钟/15 分钟）**、**Inode 用量**、**磁盘吞吐（读写）**、**IOPS（读写）**、**网络带宽**和**容器组状态**。您可以在 KubeSphere 中自定义时间范围和时间间隔以查看物理资源的历史监控数据。以下简要介绍每个监控指标。
|
||||
您可以利用**物理资源监控**页面提供的数据更好地掌控物理资源状态，并建立正常资源和集群性能的标准。KubeSphere 允许用户查看最近 7 天的集群监控数据，包括 **CPU 用量**、**内存用量**、**CPU 平均负载（1 分钟/5 分钟/15 分钟）**、**磁盘用量**、**Inode 用量**、**磁盘吞吐（读写）**、**IOPS（读写）**、**网络带宽**和**容器组状态**。您可以在 KubeSphere 中自定义时间范围和时间间隔以查看物理资源的历史监控数据。以下简要介绍每个监控指标。
|
||||
|
||||
### CPU 用量
|
||||
|
||||
|
|
@ -73,7 +73,7 @@ KubeSphere 为用户提供了 1 分钟、5 分钟和 15 分钟三种不同的平
|
|||
|
||||
### 磁盘用量
|
||||
|
||||
KubeSphere 的工作负载（例如 `StatefulSets` 和 `DaemonSets`）都依赖于持久卷。某些组件和服务也需要持久卷。这种后端存储依赖于磁盘，例如块存储或网络共享存储。因此，实时的磁盘用量监控环境对确保数据的高可靠性尤为重要。
|
||||
KubeSphere 的工作负载（例如`有状态副本集`和`守护进程集`）都依赖于持久卷。某些组件和服务也需要持久卷。这种后端存储依赖于磁盘，例如块存储或网络共享存储。因此，实时的磁盘用量监控环境对确保数据的高可靠性尤为重要。
|
||||
|
||||
在 Linux 系统的日常管理中，平台管理员可能会遇到磁盘空间不足导致数据丢失甚至系统崩溃的情况。作为集群管理的重要组成部分，平台管理员需要密切关注系统的磁盘使用情况，并确保文件系统不会被用尽或滥用。通过监控磁盘使用的历史数据，您可以评估特定时间范围内磁盘的使用情况。在磁盘用量较高的情况下，您可以通过清理不必要的镜像或容器来释放磁盘空间。
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ KubeSphere 还具有内置策略，一旦满足为这些策略定义的条件，
|
|||
|
||||
## 查看告警策略
|
||||
|
||||
在**告警策略**页面，点击一个告警策略的名称查看其详情，包括告警规则和历史。您还可以看到创建告警策略时基于所使用模板的告警规则表达式。
|
||||
在**告警策略**页面，点击一个告警策略的名称查看其详情，包括告警规则和告警历史。您还可以看到创建告警策略时基于所使用模板的告警规则表达式。
|
||||
|
||||
在**监控**下，**告警监控**图显示一段时间内的实际资源使用情况或使用量。**告警消息**显示您在通知中设置的自定义消息。
|
||||
|
||||
|
|
|
|||
|
|
@ -28,6 +28,6 @@ kubectl patch users <USERNAME> -p '{"spec":{"password":"<YOURPASSWORD>"}}' --typ
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
请将命令中的 `<USERNAME>` 修改为实际的帐户名称，将 `<YOURPASSWORD>` 修改为实际的新密码。
|
||||
请将命令中的 `<USERNAME>` 修改为实际的用户名，将 `<YOURPASSWORD>` 修改为实际的新密码。
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -6,7 +6,7 @@ linkTitle: "移除 KubeSphere 中的内置应用"
|
|||
Weight: 16910
|
||||
---
|
||||
|
||||
作为一个以应用为中心的开源容器平台，KubeSphere 在基于 [OpenPitrix](https://github.com/openpitrix/openpitrix) 的应用商店中集成了 17 个内置应用。这些应用可供企业空间内的所有租户使用，但您也可以将这些应用从应用商店中移除。本教程为您演示怎样从应用商店中移除内置应用。
|
||||
作为一个以应用为中心的开源容器平台，KubeSphere 在基于 [OpenPitrix](https://github.com/openpitrix/openpitrix) 的应用商店中集成了应用。这些应用可供企业空间内的所有租户使用，但您也可以将这些应用从应用商店中移除。本教程为您演示怎样从应用商店中移除内置应用。
|
||||
|
||||
## 准备工作
|
||||
|
||||
|
|
@ -17,7 +17,7 @@ Weight: 16910
|
|||
|
||||
1. 以 `admin` 身份登录 Web 控制台，点击左上角**平台管理**，然后选择**应用商店管理**。
|
||||
|
||||
2. 在**应用商店**页面，您可以看到列表中展示了 17 个内置应用。选择您想要从应用商店中移除的应用，例如，点击 **Tomcat** 跳转到其详情页面。
|
||||
2. 在**应用**页面，您可以看到列表中展示的应用。选择您想要从应用商店中移除的应用，例如，点击 **Tomcat** 跳转到其详情页面。
|
||||
|
||||
3. 在 Tomcat 的详情页面，点击**下架应用**以移除应用。
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ weight: 6600
|
|||
定制资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `alerting`，将 `enabled` 的 `false` 更改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@ linkTitle: "KubeSphere 应用商店"
|
|||
weight: 6200
|
||||
---
|
||||
|
||||
作为一个开源的、以应用为中心的容器平台，KubeSphere 在 [OpenPitrix](https://github.com/openpitrix/openpitrix) 的基础上，为用户提供了一个基于 Helm 的应用商店，用于应用生命周期管理。OpenPitrix 是一个开源的 Web 平台，用于打包、部署和管理不同类型的应用。KubeSphere 应用商店让 ISV、开发者和用户能够在一站式服务中只需点击几下就可以上传、测试、部署和发布应用。
|
||||
作为一个开源的、以应用为中心的容器平台，KubeSphere 在 [OpenPitrix](https://github.com/openpitrix/openpitrix) 的基础上，为用户提供了一个基于 Helm 的应用商店，用于应用生命周期管理。OpenPitrix 是一个开源的 Web 平台，用于打包、部署和管理不同类型的应用。KubeSphere 应用商店让 ISV、开发者和用户能够在一站式服务中只需点击几下就可以上传、测试、安装和发布应用。
|
||||
|
||||
对内，KubeSphere 应用商店可以作为不同团队共享数据、中间件和办公应用的场所。对外，有利于设立构建和交付的行业标准。默认情况下，应用商店中内置了 17 个应用。启用该功能后，您可以通过应用模板添加更多应用。
|
||||
对内，KubeSphere 应用商店可以作为不同团队共享数据、中间件和办公应用的场所。对外，有利于设立构建和交付的行业标准。启用该功能后，您可以通过应用模板添加更多应用。
|
||||
|
||||
有关更多信息，请参阅[应用商店](../../application-store/)。
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ weight: 6200
|
|||
定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `openpitrix`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
@ -101,12 +101,12 @@ weight: 6200
|
|||
|
||||
## 验证组件的安装
|
||||
|
||||
在您登录控制台后，如果您能看到页面左上角的**应用商店**以及其中的 17 个内置应用，则说明安装成功。
|
||||
在您登录控制台后，如果您能看到页面左上角的**应用商店**以及其中的应用，则说明安装成功。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
- 您可以在不登录控制台的情况下直接访问 `<节点 IP 地址>:30880/apps` 进入应用商店。
|
||||
- KubeSphere 3.2 中的应用商店启用后，**OpenPitrix** 页签不会显示在**系统组件**页面。
|
||||
- KubeSphere 3.2.0 中的应用商店启用后，**OpenPitrix** 页签不会显示在**系统组件**页面。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
|
|||
定制资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `auditing`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
@ -148,7 +148,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
|
|||
|
||||
{{< tab "在仪表板中验证组件的安装" >}}
|
||||
|
||||
验证您可以使用右下角**工具箱**中的**操作审计**功能。
|
||||
验证您可以使用右下角**工具箱**中的**审计日志查询**功能。
|
||||
|
||||
{{</ tab >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
|
|||
定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `devops`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `events`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
@ -154,7 +154,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
|
|||
|
||||
{{< tab "在仪表板中验证组件的安装" >}}
|
||||
|
||||
验证您可以使用右下角**工具箱**中的**事件查询**功能。
|
||||
验证您可以使用右下角**工具箱**中的**资源事件查询**功能。
|
||||
|
||||
{{</ tab >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上
|
|||
定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
|
||||
4. 在该配置文件中，搜寻到 `kubeedge.enabled`，将 `false` 更改为 `true` 以启用 KubeEdge。
|
||||
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `logging`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/metrics-server/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/metrics-server/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，导航到 `metrics_server`，在 `enabled` 一行将 `false` 更改为 `true`。完成后，点击右下角的**确定**以保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ weight: 6900
|
|||
定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `network.networkpolicy`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ CPU 和内存的资源请求和限制均指单个副本的要求。
|
|||
|
||||
| 命名空间 | openpitrix-system |
|
||||
| -------- | -------------------------------------------- |
|
||||
| CPU 请求 | 0.3 core |
|
||||
| CPU 请求 | 0.3 核 |
|
||||
| CPU 限制 | |
|
||||
| 内存请求 | 300 MiB |
|
||||
| 内存限制 | |
|
||||
|
|
@ -38,7 +38,7 @@ CPU 和内存的资源请求和限制均指单个副本的要求。
|
|||
| 命名空间 | kubesphere-devops-system | kubesphere-devops-system |
|
||||
| -------- | ------------------------------------------------------------ | -------------------------------- |
|
||||
| 安装模式 | All-in-One 安装 | 多节点安装 |
|
||||
| CPU 请求 | 34 m | 0.47 core |
|
||||
| CPU 请求 | 34 m | 0.47 核 |
|
||||
| CPU 限制 | | |
|
||||
| 内存请求 | 2.69 G | 8.6 G |
|
||||
| 内存限制 | | |
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ weight: 6920
|
|||
定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
|
||||
4. 在该配置文件中，搜寻到 `network`，将 `network.ippool.type` 更改为 `calico`。完成后，点击右下角的**确定**保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "KubeSphere 服务网格"
|
|||
weight: 6800
|
||||
---
|
||||
|
||||
KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和流量管理可视化。它拥有强大的工具包，包括**熔断机制、蓝绿部署、金丝雀发布、流量镜像、分布式链路追踪、可观测性和流量控制**等。KubeSphere 服务网格支持代码无侵入的微服务治理，帮助开发者快速上手，Istio 的学习曲线也极大降低。KubeSphere 服务网格的所有功能都旨在满足用户的业务需求。
|
||||
KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和流量管理可视化。它拥有强大的工具包，包括**熔断机制、蓝绿部署、金丝雀发布、流量镜像、链路追踪、可观测性和流量控制**等。KubeSphere 服务网格支持代码无侵入的微服务治理，帮助开发者快速上手，Istio 的学习曲线也极大降低。KubeSphere 服务网格的所有功能都旨在满足用户的业务需求。
|
||||
|
||||
有关更多信息，请参见[灰度发布](../../project-user-guide/grayscale-release/overview/)。
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
|
|||
定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px">，选择**编辑 YAML**。
|
||||
|
||||
4. 在该 YAML 文件中，搜寻到 `servicemesh`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ weight: 6915
|
|||
定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png" height="20px">，然后选择**编辑 YAML**。
|
||||
|
||||
4. 在该配置文件中，搜寻到 `network`，将 `network.topology.type` 更改为 `weave-scope`。完成后，点击右下角的**确定**保存配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: "KubeSphere v3.2.0 卸载可插拔组件"
|
||||
title: "KubeSphere 3.2.0 卸载可插拔组件"
|
||||
keywords: "Installer, uninstall, KubeSphere, Kubernetes"
|
||||
description: "学习如何在 KubeSphere v3.2.0 卸载所有可插拔组件。"
|
||||
linkTitle: "KubeSphere v3.2.0 卸载可插拔组件"
|
||||
description: "学习如何在 KubeSphere 3.2.0 卸载所有可插拔组件。"
|
||||
linkTitle: "KubeSphere 3.2.0 卸载可插拔组件"
|
||||
Weight: 6940
|
||||
---
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ Weight: 6940
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
KubeSphere v3.2.0 卸载某些可插拔组件的方法与 KubeSphere v3.0.0 不相同。有关 KubeSphere v3.0.0 卸载可插拔组件的详细方法，请参见[从 KubeSphere 上卸载可插拔组件](https://v3-0.docs.kubesphere.io/zh/docs/faq/installation/uninstall-pluggable-components/)。
|
||||
KubeSphere 3.2.0 卸载某些可插拔组件的方法与 KubeSphere v3.0.0 不相同。有关 KubeSphere v3.0.0 卸载可插拔组件的详细方法，请参见[从 KubeSphere 上卸载可插拔组件](https://v3-0.docs.kubesphere.io/zh/docs/faq/installation/uninstall-pluggable-components/)。
|
||||
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -147,7 +147,7 @@ kubectl -n kubesphere-system edit clusterconfiguration ks-installer
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
KubeSphere v3.2.0 通知系统为默认安装，您无需卸载。
|
||||
KubeSphere 3.2.0 通知系统为默认安装，您无需卸载。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ weight: 2600
|
|||
定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
|
||||
{{</ notice >}}
|
||||
|
||||
3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑 YAML**。
|
||||
3. 在**自定义资源**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑 YAML**。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ KubeSphere 支持租户隔离的审计日志查询。本教程演示了如何使
|
|||
|
||||
## 进入查询界面
|
||||
|
||||
1. 所有用户都可以使用该查询功能。使用任意帐户登录控制台，在右下角的**工具箱**图标上悬停，然后在弹出菜单中选择**操作审计**。
|
||||
1. 所有用户都可以使用该查询功能。使用任意帐户登录控制台，在右下角的**工具箱**图标上悬停，然后在弹出菜单中选择**审计日志查询**。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ KubeSphere 支持租户隔离的审计日志查询。本教程演示了如何使
|
|||
|
||||
|
||||
|
||||
3. **操作审计**控制台支持以下查询参数：
|
||||
3. **审计日志查询**控制台支持以下查询参数：
|
||||
|
||||
<table>
|
||||
<tbody>
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Kubernetes 事件系统用于深入了解集群内部发生的事件，KubeSpher
|
|||
|
||||
## 查询事件
|
||||
|
||||
1. 所有用户都可以使用事件查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/zh-cn/toolbox/event-query/toolbox.png" width="20" /> 上悬停，然后在弹出菜单中选择**事件查询**。
|
||||
1. 所有用户都可以使用事件查询功能。使用任意帐户登录控制台，在右下角的 <img src="/images/docs/zh-cn/toolbox/event-query/toolbox.png" width="20" /> 上悬停，然后在弹出菜单中选择**资源事件查询**。
|
||||
|
||||
2. 在弹出窗口中，您可以看到该帐户有权限查看的事件数量。
|
||||
|
||||
|
|
|
|||
|
|
@ -11,4 +11,4 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
---
|
||||
|
||||
本章演示集群管理员如何将 KubeSphere 升级到 v3.2.0。
|
||||
本章演示集群管理员如何将 KubeSphere 升级到 3.2.0。
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "使用 ks-installer 离线升级"
|
||||
keywords: "离线环境, 升级, kubesphere, v3.2.0"
|
||||
keywords: "离线环境, 升级, kubesphere, 3.2.0"
|
||||
description: "使用 ks-installer 和离线包升级 KubeSphere。"
|
||||
linkTitle: "使用 ks-installer 离线升级"
|
||||
weight: 7500
|
||||
|
|
@ -15,7 +15,7 @@ weight: 7500
|
|||
- 请仔细阅读 [Release Notes for 3.2.0](../../release/release-v320/)。
|
||||
- 提前备份所有重要的组件。
|
||||
- Docker 仓库。您需要有一个 Harbor 或其他 Docker 仓库。有关更多信息，请参见[准备一个私有镜像仓库](../../installing-on-linux/introduction/air-gapped-installation/#步骤-2准备一个私有镜像仓库)。
|
||||
- KubeSphere v3.2.0 支持的 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.5 和 v1.22.1。
|
||||
- KubeSphere 3.2.0 支持的 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.x 和 v1.22.x（实验性支持）。
|
||||
|
||||
## 步骤 1：准备安装镜像
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "使用 KubeKey 离线升级"
|
||||
keywords: "离线环境, kubernetes, 升级, kubesphere, v3.2.0"
|
||||
keywords: "离线环境, kubernetes, 升级, kubesphere, 3.2.0"
|
||||
description: "使用离线包升级 Kubernetes 和 KubeSphere。"
|
||||
linkTitle: "使用 KubeKey 离线升级"
|
||||
weight: 7400
|
||||
|
|
@ -47,7 +47,7 @@ weight: 7400
|
|||
|
||||
### 步骤 1：下载 KubeKey
|
||||
|
||||
与在 Linux 上在线安装 KubeSphere 相似，您需要事先[下载 KubeKey v1.1.0](https://github.com/kubesphere/kubekey/releases)。下载 `tar.gz` 文件，将它传输到充当任务机的本地机器上进行安装。解压文件后，执行以下命令，使 `kk` 可执行：
|
||||
与在 Linux 上在线安装 KubeSphere 相似，您需要事先[下载 KubeKey v1.2.0](https://github.com/kubesphere/kubekey/releases)。下载 `tar.gz` 文件，将它传输到充当任务机的本地机器上进行安装。解压文件后，执行以下命令，使 `kk` 可执行：
|
||||
|
||||
```bash
|
||||
chmod +x kk
|
||||
|
|
@ -113,7 +113,7 @@ chmod +x kk
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
- 您可以根据自己的需求变更下载的 Kubernetes 版本。安装 KubeSphere v3.2.0 的建议 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.x 以及 v1.22.x（实验性支持）。如果不指定 Kubernetes 版本，KubeKey 将默认安装 Kubernetes v1.21.5。有关受支持的 Kubernetes 版本的更多信息，请参见[支持矩阵](../../installing-on-linux/introduction/kubekey/#支持矩阵)。
|
||||
- 您可以根据自己的需求变更下载的 Kubernetes 版本。安装 KubeSphere 3.2.0 的建议 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.x 以及 v1.22.x（实验性支持）。如果不指定 Kubernetes 版本，KubeKey 将默认安装 Kubernetes v1.21.5。有关受支持的 Kubernetes 版本的更多信息，请参见[支持矩阵](../../installing-on-linux/introduction/kubekey/#支持矩阵)。
|
||||
|
||||
- 您可以通过下载 Kubernetes v1.17.9 二进制文件将 Kubernetes 从 v1.16.13 升级到 v1.17.9。但对于跨多个版本升级，需要事先下载所有中间版本，例如您想将 Kubernetes 从 v1.15.12 升级到 v1.18.6，则需要下载 Kubernetes v1.16.13、v1.17.9 和 v1.18.6 二进制文件。
|
||||
|
||||
|
|
@ -160,7 +160,7 @@ chmod +x kk
|
|||
| | Kubernetes | KubeSphere |
|
||||
| ------ | ---------- | ---------- |
|
||||
| 升级前 | v1.18.6 | v3.1.x |
|
||||
| 升级后 | v1.21.5 | v3.2.0 |
|
||||
| 升级后 | v1.21.5 | 3.2.0 |
|
||||
|
||||
#### 升级集群
|
||||
|
||||
|
|
@ -218,7 +218,7 @@ chmod +x kk
|
|||
privateRegistry: dockerhub.kubekey.local
|
||||
```
|
||||
|
||||
#### 将单节点集群升级至 KubeSphere v3.2.0 和 Kubernetes v1.21.5
|
||||
#### 将单节点集群升级至 KubeSphere 3.2.0 和 Kubernetes v1.21.5
|
||||
|
||||
```bash
|
||||
./kk upgrade -f config-sample.yaml
|
||||
|
|
@ -248,7 +248,7 @@ chmod +x kk
|
|||
| | Kubernetes | KubeSphere |
|
||||
| ------ | ---------- | ---------- |
|
||||
| 升级前 | v1.18.6 | v3.1.x |
|
||||
| 升级后 | v1.21.5 | v3.2.0 |
|
||||
| 升级后 | v1.21.5 | 3.2.0 |
|
||||
|
||||
#### 升级集群
|
||||
|
||||
|
|
@ -308,7 +308,7 @@ chmod +x kk
|
|||
privateRegistry: dockerhub.kubekey.local
|
||||
```
|
||||
|
||||
#### 将多节点集群升级至 KubeSphere v3.2.0 和 Kubernetes v1.21.5
|
||||
#### 将多节点集群升级至 KubeSphere 3.2.0 和 Kubernetes v1.21.5
|
||||
|
||||
```bash
|
||||
./kk upgrade -f config-sample.yaml
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "概述"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, v3.2.0, 升级"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, 3.2.0, 升级"
|
||||
description: "了解升级之前需要注意的事项，例如版本和升级工具。"
|
||||
linkTitle: "概述"
|
||||
weight: 7100
|
||||
|
|
@ -8,11 +8,11 @@ weight: 7100
|
|||
|
||||
## 确定您的升级方案
|
||||
|
||||
KubeSphere v3.2.0 与 Kubernetes 1.19.x、1.20.x、1.21.5 以及 1.22.1 兼容：
|
||||
KubeSphere 3.2.0 与 Kubernetes 1.19.x、1.20.x、1.21.x 以及 1.22.x（实验性支持）兼容：
|
||||
|
||||
- 在您升级集群至 KubeSphere v3.2.0 之前，您的 KubeSphere 集群版本必须为 v3.1.x。
|
||||
- 在您升级集群至 KubeSphere 3.2.0 之前，您的 KubeSphere 集群版本必须为 v3.1.x。
|
||||
|
||||
- 如果您的现有 KubeSphere v3.1.x 集群安装在 Kubernetes 1.19.x+ 上，您可选择只将 KubeSphere 升级到 v3.2.0 或者同时升级 Kubernetes（到更高版本）和 KubeSphere（到 v3.2.0）。
|
||||
- 如果您的现有 KubeSphere v3.1.x 集群安装在 Kubernetes 1.19.x+ 上，您可选择只将 KubeSphere 升级到 3.2.0 或者同时升级 Kubernetes（到更高版本）和 KubeSphere（到 3.2.0）。
|
||||
|
||||
## 升级前
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ weight: 7300
|
|||
- 您需要有一个运行 KubeSphere v3.1.x 的集群。如果您的 KubeSphere 是 v3.0.0 或更早的版本，请先升级至 v3.1.x。
|
||||
- 请仔细阅读 [Release Notes for 3.2.0](../../release/release-v320/)。
|
||||
- 提前备份所有重要的组件。
|
||||
- KubeSphere v3.2.0 支持的 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.5 和 v1.22.1。
|
||||
- KubeSphere v3.2.0 支持的 Kubernetes 版本：v1.19.x、v1.20.x、v1.21.x 和 v1.22.x（实验性支持）。
|
||||
|
||||
## 应用 ks-installer
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: "使用 KubeKey 升级"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, v3.2.0, KubeKey"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, 3.2.0, KubeKey"
|
||||
description: "使用 KubeKey 升级 Kubernetes 和 KubeSphere。"
|
||||
linkTitle: "使用 KubeKey 升级"
|
||||
weight: 7200
|
||||
|
|
@ -81,7 +81,7 @@ chmod +x kk
|
|||
|
||||
### All-in-One 集群
|
||||
|
||||
运行以下命令使用 KubeKey 将您的单节点集群升级至 KubeSphere v3.2.0 和 Kubernetes v1.21.5：
|
||||
运行以下命令使用 KubeKey 将您的单节点集群升级至 KubeSphere 3.2.0 和 Kubernetes v1.21.5：
|
||||
|
||||
```bash
|
||||
./kk upgrade --with-kubernetes v1.21.5 --with-kubesphere v3.2.0
|
||||
|
|
@ -127,7 +127,7 @@ chmod +x kk
|
|||
|
||||
#### 步骤 3：升级集群
|
||||
|
||||
运行以下命令，将您的集群升级至 KubeSphere v3.2.0 和 Kubernetes v1.21.5：
|
||||
运行以下命令，将您的集群升级至 KubeSphere 3.2.0 和 Kubernetes v1.21.5：
|
||||
|
||||
```bash
|
||||
./kk upgrade --with-kubernetes v1.21.5 --with-kubesphere v3.2.0 -f sample.yaml
|
||||
|
|
@ -142,6 +142,6 @@ chmod +x kk
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
若要使用 KubeSphere v3.2.0 的部分新功能，您需要在升级后启用对应的可插拔组件。
|
||||
若要使用 KubeSphere 3.2.0 的部分新功能，您需要在升级后启用对应的可插拔组件。
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -1,13 +1,13 @@
|
|||
---
|
||||
title: "升级后的变更"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, v3.2.0"
|
||||
keywords: "Kubernetes, 升级, KubeSphere, 3.2.0"
|
||||
description: "了解升级后的变更。"
|
||||
|
||||
linkTitle: "升级后的变更"
|
||||
weight: 7600
|
||||
---
|
||||
|
||||
本文说明先前版本现有设置在升级后的变更。如果您想了解 KubeSphere 3.2.0 的所有新功能和优化，请直接参阅 [v3.2.0 发布说明](../../release/release-v320/)。
|
||||
本文说明先前版本现有设置在升级后的变更。如果您想了解 KubeSphere 3.2.0 的所有新功能和优化，请直接参阅 [3.2.0 发布说明](../../release/release-v320/)。
|
||||
|
||||
## 访问控制
|
||||
|
||||
|
|
|
|||
|
|
@ -33,6 +33,6 @@ KubeSphere 提供应用程序的全生命周期管理。例如，企业空间管
|
|||
|
||||
5. 成功上传后，模板列表中会列出应用，状态为**开发中**，意味着该应用正在开发中。上传的应用对同一企业空间下的所有成员均可见。
|
||||
|
||||
6. 点击应用，随后打开的页面默认选中**版本**标签。点击待提交版本以展开菜单，您可以在菜单上看到**删除**、**测试安装**、**提交审核**的选项。
|
||||
6. 点击应用，随后打开的页面默认选中**版本**标签。点击待提交版本以展开菜单，您可以在菜单上看到**删除**、**测试**、**提交发布**的选项。
|
||||
|
||||
7. 有关如何将应用发布到应用商店的更多信息，请参考[应用程序生命周期管理](../../application-store/app-lifecycle-management/)。
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ weight: 9700
|
|||
|
||||
3. **企业空间配额**页面列有分配到该企业空间的全部可用集群，以及各集群的 CPU 限额、CPU 需求、内存限额和内存需求。
|
||||
|
||||
4. 在列表右侧点击**编辑企业空间配额**即可查看企业空间配额信息。默认情况下，KubeSphere 不为企业空间设置任何资源预留或资源限制。如需设置资源预留或资源限制来管理 CPU 和内存资源，您可以移动 <img src="/images/docs/common-icons/slider.png" width="20" /> 至期望数值或直接输入期望数值。将字段设为空值表示不对资源进行预留或限制。
|
||||
4. 在列表右侧点击**编辑配额**即可查看企业空间配额信息。默认情况下，KubeSphere 不为企业空间设置任何资源预留或资源限制。如需设置资源预留或资源限制来管理 CPU 和内存资源，您可以移动 <img src="/images/docs/common-icons/slider.png" width="20" /> 至期望数值或直接输入期望数值。将字段设为空值表示不对资源进行预留或限制。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue