mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Merge pull request #1635 from rodmiromind/release-3.0
Add interlinks and minor content changes
This commit is contained in:
KubeSphere CI Bot
GitHub
commit
aeeca6b405
|
|
@ -14,7 +14,7 @@ In a world where Kubernetes has become the de facto standard to build applicatio
|
|||
|
||||
|
||||
|
||||
In addition to TiDB, I am also using [KubeSphere](https://kubesphere.io/), an open-source distributed operating system that manages cloud-native applications with [Kubernetes](https://kubernetes.io/) as its kernel. It provides a plug-and-play architecture for the seamless integration of third-party applications to boost its ecosystem. [KubeSphere can be run anywhere](https://kubesphere.io/docs/introduction/what-is-kubesphere/#run-kubesphere-everywhere) as it is highly pluggable without any hacking into Kubernetes.
|
||||
In addition to TiDB, I am also using KubeSphere [Container Platform](https://kubesphere.io/), an open-source distributed operating system that manages cloud-native applications with [Kubernetes](https://kubernetes.io/) as its kernel. It provides a plug-and-play architecture for the seamless integration of third-party applications to boost its ecosystem. [KubeSphere can be run anywhere](https://kubesphere.io/docs/introduction/what-is-kubesphere/#run-kubesphere-everywhere) as it is highly pluggable without any hacking into Kubernetes.
|
||||
|
||||
|
||||
|
||||
|
|
@ -243,4 +243,4 @@ If you have any questions, don't hesitate to contact us in [Slack](https://join.
|
|||
|
||||
**KubeSphere Introduction**: https://kubesphere.io/docs/introduction/what-is-kubesphere/
|
||||
|
||||
**KubeSphere Documentation**: https://kubesphere.io/docs/
|
||||
**KubeSphere Documentation**: https://kubesphere.io/docs/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Multi-tenancy in KubeSphere"
|
||||
title: "Kubernetes Multi-tenancy in KubeSphere"
|
||||
keywords: "Kubernetes, Kubesphere, multi-tenancy"
|
||||
description: "Understand the multi-tenant architecture in KubeSphere."
|
||||
linkTitle: "Multi-tenancy in KubeSphere"
|
||||
|
|
@ -12,7 +12,7 @@ The first and foremost challenge is how to define multi-tenancy in an enterprise
|
|||
|
||||
## Challenges in Kubernetes Multi-tenancy
|
||||
|
||||
Multi-tenancy is a common software architecture. Resources in a multi-tenant environment are shared by multiple users, also known as "tenants", with their respective data isolated from each other. The administrator of a multi-tenant cluster must minimize the damage that a compromised or malicious tenant can do to others and make sure resources are fairly allocated.
|
||||
Multi-tenancy is a common software architecture. Resources in a multi-tenant environment are shared by multiple users, also known as "tenants", with their respective data isolated from each other. The administrator of a multi-tenant Kubernetes cluster must minimize the damage that a compromised or malicious tenant can do to others and make sure resources are fairly allocated.
|
||||
|
||||
No matter how an enterprise multi-tenant system is structured, it always comes with the following two building blocks: logical resource isolation and physical resource isolation.
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ Logically, resource isolation mainly entails API access control and tenant-based
|
|||
|
||||
The isolation of physical resources includes nodes and networks, while it also relates to container runtime security. For example, you can create [NetworkPolicy](../../pluggable-components/network-policy/) resources to control traffic flow and use PodSecurityPolicy objects to control container behavior. [Kata Containers](https://katacontainers.io/) provides a more secure container runtime.
|
||||
|
||||
## Multi-tenancy in KubeSphere
|
||||
## Kubernetes Multi-tenancy in KubeSphere
|
||||
|
||||
To solve the issues above, KubeSphere provides a multi-tenant management solution based on Kubernetes.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Cluster Shutdown and Restart"
|
||||
title: "Kubernetes Cluster Shutdown and Restart"
|
||||
description: "Learn how to gracefully shut down your cluster and restart it."
|
||||
layout: "single"
|
||||
|
||||
|
|
@ -8,7 +8,7 @@ weight: 8800
|
|||
|
||||
icon: "/images/docs/docs.svg"
|
||||
---
|
||||
This document describes the process of gracefully shutting down your cluster and how to restart it. You might need to temporarily shut down your cluster for maintenance reasons.
|
||||
This document describes the process of gracefully shutting down your Kubernetes cluster and how to restart it. You might need to temporarily shut down your cluster for maintenance reasons.
|
||||
|
||||
{{< notice warning >}}
|
||||
Shutting down a cluster is very dangerous. You must fully understand the operation and its consequences. Please make an etcd backup before you proceed.
|
||||
|
|
@ -42,7 +42,7 @@ done
|
|||
Then you can shut down other cluster dependencies, such as external storage.
|
||||
|
||||
## Restart a Cluster Gracefully
|
||||
You can restart a cluster gracefully after shutting down the cluster gracefully.
|
||||
You can restart a Kubernetes cluster gracefully after shutting down the cluster gracefully.
|
||||
|
||||
### Prerequisites
|
||||
You have shut down your cluster gracefully.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ linkTitle: "Integrate SonarQube into Pipelines"
|
|||
weight: 11310
|
||||
---
|
||||
|
||||
[SonarQube](https://www.sonarqube.org/) is a popular continuous inspection tool for code quality. You can use it for static and dynamic analysis of a codebase. After it is integrated into pipelines in KubeSphere, you can view common code issues such as bugs and vulnerabilities directly on the dashboard as SonarQube detects issues in a running pipeline.
|
||||
[SonarQube](https://www.sonarqube.org/) is a popular continuous inspection tool for code quality. You can use it for static and dynamic analysis of a codebase. After it is integrated into pipelines in KubeSphere [Container Platform](https://kubesphere.io/), you can view common code issues such as bugs and vulnerabilities directly on the dashboard as SonarQube detects issues in a running pipeline.
|
||||
|
||||
This tutorial demonstrates how you can integrate SonarQube into pipelines. Refer to the following steps first before you [create a pipeline using a Jenkinsfile](../../../devops-user-guide/how-to-use/create-a-pipeline-using-jenkinsfile/).
|
||||
|
||||
|
|
@ -281,4 +281,4 @@ You need a SonarQube token so that your pipeline can communicate with SonarQube
|
|||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -194,4 +194,4 @@ Now that your own Prometheus stack is up and running, you can change KubeSphere'
|
|||
|
||||
If you enable/disable KubeSphere pluggable components following [this guide](https://kubesphere.io/docs/pluggable-components/overview/) , the `monitoring endpoint` will be reset to the original one. In this case, you have to change it to the new one and then restart the KubeSphere APIServer again.
|
||||
|
||||
{{</ notice >}}
|
||||
{{</ notice >}}
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: "Horizontal Pod Autoscaling"
|
||||
title: "Kubernetes HPA (Horizontal Pod Autoscaling) on KubeSphere"
|
||||
keywords: "Horizontal, Pod, Autoscaling, Autoscaler"
|
||||
description: "How to configure Horizontal Pod Autoscaling on KubeSphere."
|
||||
description: "How to configure Kubernetes Horizontal Pod Autoscaling on KubeSphere."
|
||||
weight: 10290
|
||||
|
||||
---
|
||||
|
||||
This document describes how to configure Horizontal Pod Autoscaling (HPA) on KubeSphere.
|
||||
|
||||
The HPA feature automatically adjusts the number of Pods to maintain average resource usage (CPU and memory) of Pods around preset values. For details about how HPA functions, see the [official Kubernetes document](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).
|
||||
The Kubernetes HPA feature automatically adjusts the number of Pods to maintain average resource usage (CPU and memory) of Pods around preset values. For details about how HPA functions, see the [official Kubernetes document](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).
|
||||
|
||||
This document uses HPA based on CPU usage as an example. Operations for HPA based on memory usage are similar.
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ This document uses HPA based on CPU usage as an example. Operations for HPA base
|
|||
|
||||
7. Click **Next** on the **Mount Volumes** tab and click **Create** on the **Advanced Settings** tab.
|
||||
|
||||
## Configure HPA
|
||||
## Configure Kubernetes HPA
|
||||
|
||||
1. Choose **Deployments** in **Workloads** on the left navigation bar and click the HPA Deployment (for example, hpa-v1) on the right.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "All-in-One Installation on Linux"
|
||||
title: "All-in-one Installation of Kubernetes and KubeSphere on Linux"
|
||||
keywords: 'KubeSphere, Kubernetes, All-in-one, Installation'
|
||||
description: 'Install KubeSphere on Linux with a minimal installation package. The tutorial serves as a basic kick-starter for you to understand the container platform, paving the way for learning the following guides.'
|
||||
linkTitle: "All-in-One Installation on Linux"
|
||||
|
|
@ -154,7 +154,7 @@ After you execute the command, you will see a table as below for environment che
|
|||
|
||||
## Step 4: Verify the Installation
|
||||
|
||||
When you see the output as below, it means the installation finishes.
|
||||
When you see the output as below, it means the installation of Kubernetes and KubeSphere finishes.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue