mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Merge pull request #675 from rayzhou2017/cluster-mgmt
Clean and update cluster admin including re-org index, _index content…
This commit is contained in:
KubeSphere CI Bot
GitHub
commit
912d779aff
|
|
@ -11,7 +11,7 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
---
|
||||
|
||||
In KubeSphere, you set a cluster's configuration and configure its features using the interactive web console or the built-in native command-line tool kubectl. As a cluster administrator, you are responsible for a series of tasks, including cordoning and adding labels to nodes, controlling cluster visibility, monitoring cluster status, setting cluster-wide alerting and notification rules, as well as configuring storage and log collection solutions.
|
||||
In KubeSphere, you set a cluster's configurations and configure its features using the interactive web console or the built-in native command-line tool kubectl. As a cluster administrator, you are responsible for a series of tasks, including cordoning and adding labels to nodes, controlling cluster visibility, monitoring cluster status, setting cluster-wide alerting and notification rules, as well as configuring storage and log collection solutions.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -21,11 +21,11 @@ Multi-cluster management is not covered in this chapter. For more information ab
|
|||
|
||||
## [Persistent Volume and Storage Class](../cluster-administration/persistent-volume-and-storage-class/)
|
||||
|
||||
Learn basic concepts of PVs, PVCs and storage classes, and demonstrates how to manage storage classes and PVCs in KubeSphere.
|
||||
Learn basic concepts of PVs, PVCs and storage classes, and demonstrate how to manage storage classes and PVCs in KubeSphere.
|
||||
|
||||
## [Node Management](../cluster-administration/nodes/)
|
||||
|
||||
Monitor node status and learn how to add node label or taints.
|
||||
Monitor node status and learn how to add node labels or taints.
|
||||
|
||||
## [Cluster Status Monitoring](../cluster-administration/cluster-status-monitoring/)
|
||||
|
||||
|
|
@ -51,10 +51,14 @@ Learn how to set alerting policies for nodes.
|
|||
|
||||
### [Alerting Message (Node Level)](../cluster-administration/cluster-wide-alerting-and-notification/alerting-message/)
|
||||
|
||||
Learn how to view alerting policies for nodes.
|
||||
Learn how to view alerting policies and deal with alerting messages for nodes.
|
||||
|
||||
## Cluster Settings
|
||||
|
||||
### [Cluster Visibility and Authorization](../cluster-administration/cluster-settings/cluster-visibility-and-authorization/)
|
||||
|
||||
Learn how to set up cluster visibility and authorization.
|
||||
|
||||
### Log Collections
|
||||
|
||||
#### [Introduction](../cluster-administration/cluster-settings/log-collections/introduction/)
|
||||
|
|
@ -77,10 +81,10 @@ Learn how to add Fluentd to receive logs, events or auditing logs.
|
|||
|
||||
Customize your email address settings to receive notifications of any alert.
|
||||
|
||||
## [Customizing Platform Information](../cluster-administration/platform-settings/customize-basic-information/)
|
||||
## [Platform Settings](../cluster-administration/platform-settings/)
|
||||
|
||||
Customize platform settings such as logo, title etc.
|
||||
|
||||
## [Cluster Shutdown and Restart](../cluster-administration/shuting-down-and-restart-cluster-cracefully/)
|
||||
## [Cluster Shutdown and Restart](../cluster-administration/shut-down-and-restart-cluster-gracefully/)
|
||||
|
||||
Learn how to gracefully shutting down your cluster and how to restart it.
|
||||
Learn how to gracefully shut down your cluster and how to restart it.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Kubernetes, KubeSphere, resources, monitoring"
|
|||
description: "Monitor application resources in KubeSphere"
|
||||
|
||||
linkTitle: "Application Resources Monitoring"
|
||||
weight: 400
|
||||
weight: 9400
|
||||
---
|
||||
|
||||
In addition to monitoring data at the physical resource level, cluster administrators also need to keep a close track of application resources across the platform, such as the number of projects and DevOps projects, as well as the number of workloads and services of a specific type. Application resource monitoring provides a summary of resource usage and application-level trends of the platform.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Cluster Settings"
|
||||
weight: 4180
|
||||
weight: 9600
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Cluster Visibility, Cluster Management"
|
|||
description: "Cluster Visibility"
|
||||
|
||||
linkTitle: "Cluster Visibility and Authorization"
|
||||
weight: 200
|
||||
weight: 9610
|
||||
---
|
||||
|
||||
## Objective
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Log collection"
|
||||
weight: 2000
|
||||
weight: 9620
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, elasticsearch, pod, container, fluentbit, output'
|
|||
description: 'Add Elasticsearch as log receiver to receive container logs'
|
||||
|
||||
linkTitle: "Add Elasticsearch as Receiver"
|
||||
weight: 2200
|
||||
weight: 9622
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate how to add an Elasticsearch receiver.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, fluentd, pod, container, fluentbit, output'
|
|||
description: 'KubeSphere Installation Overview'
|
||||
|
||||
linkTitle: "Add Fluentd as Receiver"
|
||||
weight: 2400
|
||||
weight: 9624
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, kafka, pod, container, fluentbit, output'
|
|||
description: 'KubeSphere Installation Overview'
|
||||
|
||||
linkTitle: "Add Kafka as Receiver"
|
||||
weight: 2300
|
||||
weight: 9623
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, elasticsearch, kafka, fluentd, pod, container, fluen
|
|||
description: 'Add log receivers to receive container logs'
|
||||
|
||||
linkTitle: "Introduction"
|
||||
weight: 2100
|
||||
weight: 9621
|
||||
---
|
||||
|
||||
KubeSphere provides a flexible log collection configuration method. Powered by [FluentBit Operator](https://github.com/kubesphere/fluentbit-operator/), users can add/modify/delete/enable/disable Elasticsearch, Kafka and Fluentd receivers with ease. Once a receiver is added, logs will be sent to this receiver.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Notification, Mail Server'
|
|||
description: 'Mail Server'
|
||||
|
||||
linkTitle: "Mail Server"
|
||||
weight: 4190
|
||||
weight: 9630
|
||||
---
|
||||
|
||||
## Objective
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Kubernetes, KubeSphere, status, monitoring"
|
|||
description: "Monitor cluster resources in KubeSphere"
|
||||
|
||||
linkTitle: "Cluster Status Monitoring"
|
||||
weight: 300
|
||||
weight: 9300
|
||||
---
|
||||
|
||||
KubeSphere provides monitoring of related metrics such as CPU, memory, network, and disk of the cluster. You can also review historical monitoring data and sort nodes by different indicators based on their usage in **Cluster Status Monitoring**.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Cluster-wide Alerting and Notification"
|
||||
weight: 2000
|
||||
weight: 9500
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Node, Alerting, Message, Notification'
|
|||
description: 'How to view alerting messages at the node level.'
|
||||
|
||||
linkTitle: "Alerting Message (Node Level)"
|
||||
weight: 4170
|
||||
weight: 9540
|
||||
---
|
||||
|
||||
Alert messages record detailed information of alerts triggered based on alert rules, including monitoring targets, alert policies, recent notifications and comments.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Node, Alerting, Policy, Notification'
|
|||
description: 'How to set alerting policies at the node level.'
|
||||
|
||||
linkTitle: "Alerting Policy (Node Level)"
|
||||
weight: 4160
|
||||
weight: 9530
|
||||
---
|
||||
|
||||
## Objective
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, prometheus, alertmanager, alerting'
|
|||
description: 'Manage alerts with Alertmanager in KubeSphere'
|
||||
|
||||
linkTitle: "Alertmanager in KubeSphere"
|
||||
weight: 2010
|
||||
weight: 9510
|
||||
---
|
||||
|
||||
Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts. For more details, please refer to [Alertmanager guide](https://prometheus.io/docs/alerting/latest/alertmanager/).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "kubernetes, KubeSphere, notification manager, email, wechat, slack"
|
|||
description: "K8s native notification management with multi-tenancy support"
|
||||
|
||||
linkTitle: "Notification Manager"
|
||||
weight: 2020
|
||||
weight: 9520
|
||||
---
|
||||
|
||||
[Notification Manager](https://github.com/kubesphere/notification-manager) manages notifications in KubeSphere. It receives alerts or notifications from different senders and then sends notifications to different users.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Kubernetes, KubeSphere, taints, nodes, labels, requests, limits"
|
|||
description: "Kubernetes Node Management"
|
||||
|
||||
linkTitle: "Node Management"
|
||||
weight: 200
|
||||
weight: 9200
|
||||
---
|
||||
|
||||
Kubernetes runs your workloads by placing containers into Pods to run on nodes. A node may be a virtual or physical machine, depending on the cluster. Each node contains the services necessary to run Pods, managed by the control plane. For more information about nodes, see the [official documentation of Kubernetes](https://kubernetes.io/docs/concepts/architecture/nodes/).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "storage, volume, pv, pvc, storage class, csi, Ceph RBD, Glusterfs, Qi
|
|||
description: "Persistent Volume and Storage Class Management"
|
||||
|
||||
linkTitle: "Persistent Volume and Storage Class"
|
||||
weight: 100
|
||||
weight: 9100
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
title: "Platform Settings"
|
||||
keywords: 'KubeSphere, Kubernetes, customize, platform'
|
||||
description: 'How to Customize KubeSphere Platform Information.'
|
||||
|
||||
linkTitle: "Platform Settings"
|
||||
weight: 9700
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
title: "Customizing Platform Information"
|
||||
keywords: 'KubeSphere, Kubernetes, customize, platform'
|
||||
description: 'How to Customizing KubeSphere Platform Information.'
|
||||
|
||||
linkTitle: "Customizing Platform Information"
|
||||
weight: 4270
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -4,7 +4,7 @@ description: "Demonstrate how to shut down and restart Kubernetes clusters grace
|
|||
layout: "single"
|
||||
|
||||
linkTitle: "Cluster Shutdown and Restart"
|
||||
weight: 5000
|
||||
weight: 9800
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
---
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
---
|
||||
|
||||
在 KubeSphere 中，您可以使用交互式 Web 控制台或内置的本地命令行工具 `kubectl` 设置集群并配置其功能。作为集群管理员，您将负责一系列任务，包括在节点上管理调度并添加标签，控制集群可见性，监控集群状态，设置集群的告警范围和通知规则，以及配置存储和日志收集的方案等。
|
||||
在 KubeSphere 中，您可以使用交互式 Web 控制台或内置的本地命令行工具`kubectl`设置集群并配置其功能。作为集群管理员，您将负责一系列任务，包括在节点上管理调度并添加标签，控制集群可见性，监控集群状态，设置集群的告警范围和通知规则，以及配置存储和日志收集的方案等。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -37,9 +37,9 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
## 群集范围的告警和通知
|
||||
|
||||
### [kubeSphere中的Alertmanager](../cluster-administration/cluster-wide-alerting-and-notification/alertmanager/)
|
||||
### [kubeSphere 中的 Alertmanager](../cluster-administration/cluster-wide-alerting-and-notification/alertmanager/)
|
||||
|
||||
了解如何在 KubeSphere 中使用 Alertmanager 管理警报。
|
||||
了解如何在 KubeSphere 中使用 Alertmanager 管理告警。
|
||||
|
||||
### [通知管理器](../cluster-administration/cluster-wide-alerting-and-notification/notification-manager/)
|
||||
|
||||
|
|
@ -55,6 +55,10 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
## 集群设置
|
||||
|
||||
### [集群可见性与权限](../cluster-administration/cluster-settings/cluster-visibility-and-authorization/)
|
||||
|
||||
了解如何设置集群的可见性以及授权。
|
||||
|
||||
### 日志收集
|
||||
|
||||
#### [介绍](../cluster-administration/cluster-settings/log-collections/introduction/)
|
||||
|
|
@ -77,10 +81,10 @@ icon: "/images/docs/docs.svg"
|
|||
|
||||
自定义您的电子邮件地址设置，以接收任何告警的通知。
|
||||
|
||||
## [自定义平台信息](../cluster-administration/platform-settings/customize-basic-information/)
|
||||
## [自定义平台信息](../cluster-administration/platform-settings/)
|
||||
|
||||
自定义平台设置，如 Logo、标题等。
|
||||
|
||||
## [关闭和重启集群](../cluster-administration/shuting-down-and-restart-cluster-cracefully/)
|
||||
## [关闭和重启集群](../cluster-administration/shut-down-and-restart-cluster-gracefully/)
|
||||
|
||||
了解如何优雅地关闭集群以及如何重新启动它。
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: "应用资源监控"
|
|||
keywords: "Kubernetes, KubeSphere, resources, monitoring"
|
||||
description: "Monitor application resources in KubeSphere"
|
||||
linkTitle: "应用资源监控"
|
||||
weight: 400
|
||||
weight: 9400
|
||||
---
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Cluster Settings"
|
||||
weight: 4180
|
||||
weight: 9600
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Cluster Visibility, Cluster Management"
|
|||
description: "Cluster Visibility"
|
||||
|
||||
linkTitle: "Cluster Visibility and Authorization"
|
||||
weight: 200
|
||||
weight: 9610
|
||||
---
|
||||
|
||||
## Objective
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Log collection"
|
||||
weight: 2000
|
||||
weight: 9620
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, elasticsearch, pod, container, fluentbit, output'
|
|||
description: 'Add Elasticsearch as log receiver to receive container logs'
|
||||
|
||||
linkTitle: "Add Elasticsearch as Receiver"
|
||||
weight: 2200
|
||||
weight: 9622
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate how to add an Elasticsearch receiver.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, fluentd, pod, container, fluentbit, output'
|
|||
description: 'KubeSphere Installation Overview'
|
||||
|
||||
linkTitle: "Add Fluentd as Receiver"
|
||||
weight: 2400
|
||||
weight: 9624
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, kafka, pod, container, fluentbit, output'
|
|||
description: 'KubeSphere Installation Overview'
|
||||
|
||||
linkTitle: "Add Kafka as Receiver"
|
||||
weight: 2300
|
||||
weight: 9623
|
||||
---
|
||||
KubeSphere supports using Elasticsearch, Kafka and Fluentd as log receivers.
|
||||
This doc will demonstrate:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, log, elasticsearch, kafka, fluentd, pod, container, fluen
|
|||
description: 'Add log receivers to receive container logs'
|
||||
|
||||
linkTitle: "Introduction"
|
||||
weight: 2100
|
||||
weight: 9621
|
||||
---
|
||||
|
||||
KubeSphere provides a flexible log collection configuration method. Powered by [FluentBit Operator](https://github.com/kubesphere/fluentbit-operator/), users can add/modify/delete/enable/disable Elasticsearch, Kafka and Fluentd receivers with ease. Once a receiver is added, logs will be sent to this receiver.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Notification, Mail Server'
|
|||
description: '邮件服务器'
|
||||
|
||||
linkTitle: "邮件服务器"
|
||||
weight: 4190
|
||||
weight: 9630
|
||||
---
|
||||
|
||||
## 目标
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Kubernetes， KubeSphere， status， monitoring"
|
|||
description: "kubeSphere的集群资源监控"
|
||||
|
||||
linkTitle: "集群状态监控"
|
||||
weight: 300
|
||||
weight: 9300
|
||||
---
|
||||
|
||||
KubeSphere 提供了对集群的 CPU、内存、网络和磁盘等相关指标的监控。在**集群状态监控**页面中，您还可以查看历史监控数据并根据节点的使用情况按不同的指标对节点进行排序。
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
linkTitle: "Cluster-wide Alerting and Notification"
|
||||
weight: 2000
|
||||
weight: 9500
|
||||
|
||||
_build:
|
||||
render: false
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Node, Alerting, Message, Notification'
|
|||
description: '如何在节点级别查看告警信息。'
|
||||
|
||||
linkTitle: "告警消息(节点级别)"
|
||||
weight: 4170
|
||||
weight: 9540
|
||||
---
|
||||
|
||||
告警信息记录根据警报规则触发的告警的详细信息，包括监控目标，告警策略，最近的通知和注释。
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'KubeSphere, Kubernetes, Node, Alerting, Policy, Notification'
|
|||
description: '如何在节点级设置告警策略。'
|
||||
|
||||
linkTitle: "告警策略（节点级别）"
|
||||
weight: 4160
|
||||
weight: 9530
|
||||
---
|
||||
|
||||
## 目标
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: 'kubernetes, prometheus, alertmanager, alerting'
|
|||
description: 'Manage alerts with Alertmanager in KubeSphere'
|
||||
|
||||
linkTitle: "Alertmanager in KubeSphere"
|
||||
weight: 2010
|
||||
weight: 9510
|
||||
---
|
||||
|
||||
Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts. For more details, please refer to [Alertmanager guide](https://prometheus.io/docs/alerting/latest/alertmanager/).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "kubernetes, KubeSphere, notification manager, email, wechat, slack"
|
|||
description: "K8s native notification management with multi-tenancy support"
|
||||
|
||||
linkTitle: "Notification Manager"
|
||||
weight: 2020
|
||||
weight: 9520
|
||||
---
|
||||
|
||||
[Notification Manager](https://github.com/kubesphere/notification-manager) manages notifications in KubeSphere. It receives alerts or notifications from different senders and then sends notifications to different users.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "Kubernetes, KubeSphere, taints, nodes, labels, requests, limits"
|
|||
description: "Kubernetes 节点管理"
|
||||
|
||||
linkTitle: "节点管理"
|
||||
weight: 200
|
||||
weight: 9200
|
||||
---
|
||||
|
||||
Kubernetes通过将容器放入容器组中并在节点上运行来运行工作负载。节点可以是虚拟机，也可以是物理机，这取决于集群环境。每个节点都包含运行容器组所需的服务，这些服务由控制平面管理。有关节点的更多信息，请参见[Kubernetes的官方文档](https://kubernetes.io/docs/concepts/architecture/nodes/)。
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: "storage, volume, pv, pvc, storage class, csi, Ceph RBD, Glusterfs, Qi
|
|||
description: "Persistent Volume and Storage Class Management"
|
||||
|
||||
linkTitle: "Persistent Volume and Storage Class"
|
||||
weight: 100
|
||||
weight: 9100
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
title: "Platform Settings"
|
||||
keywords: 'KubeSphere, Kubernetes, customize, platform'
|
||||
description: 'How to Customize KubeSphere Platform Information.'
|
||||
|
||||
linkTitle: "Platform Settings"
|
||||
weight: 9700
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
linkTitle: "DevOps Administration"
|
||||
weight: 2200
|
||||
|
||||
_build:
|
||||
render: false
|
||||
---
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
---
|
||||
title: "Role and Member Management"
|
||||
keywords: 'kubernetes, kubesphere, air gapped, installation'
|
||||
description: 'Role and Member Management'
|
||||
|
||||
|
||||
weight: 2240
|
||||
---
|
||||
|
||||
TBD
|
||||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: "集群关闭和重新启动"
|
||||
title: "关闭和重启集群"
|
||||
description: "Demonstrate how to shut down and restart Kubernetes clusters gracefully"
|
||||
layout: "single"
|
||||
|
||||
linkTitle: "集群关闭和重新启动"
|
||||
weight: 5000
|
||||
linkTitle: "关闭和重启集群"
|
||||
weight: 9800
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,8 +0,0 @@
|
|||
---
|
||||
title: "StorageClass"
|
||||
keywords: "kubernetes, docker, kubesphere, jenkins, istio, prometheus"
|
||||
description: "Kubernetes and KubeSphere node management"
|
||||
|
||||
linkTitle: "StorageClass"
|
||||
weight: 100
|
||||
---
|
||||
Loading…
Reference in New Issue