mirror of
https://github.com/kubesphere/website.git
synced 2025-12-30 09:42:53 +00:00
KubeSphere CI Bot
GitHub
commit
e3ea2c0cbb
|
|
@ -16,6 +16,7 @@ KubeSphere v3.0.0 is compatible with Kubernetes 1.15.x, 1.16.x, 1.17.x and 1.18.
|
|||
- If your KubeSphere v2.1.x is installed on Kubernetes 1.14.x, you have to upgrade Kubernetes (to 1.15.x+) and KubeSphere (to v3.0.0 ) at the same time.
|
||||
|
||||
{{< notice warning >}}
|
||||
|
||||
There are some significant API changes in Kubernetes 1.16.x compared with prior versions 1.14.x and 1.15.x. Please refer to [Deprecated APIs Removed In 1.16: Here’s What You Need To Know](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) for more details. So if you plan to upgrade from Kubernetes 1.14.x/1.15.x to 1.16.x+, you have to migrate some of your workloads after upgrading.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -23,6 +24,7 @@ There are some significant API changes in Kubernetes 1.16.x compared with prior
|
|||
## Before Upgrade
|
||||
|
||||
{{< notice warning >}}
|
||||
|
||||
- You are supposed to implement a simulation for the upgrade in a testing environment first. After the upgrade is successful in the testing environment and all applications are running normally, upgrade it in your production environment.
|
||||
- During the upgrade process, there may be a short interruption of applications (especially for those single-replica Pod). Please arrange a reasonable period of time for upgrade.
|
||||
- It is recommended to back up ETCD and stateful applications before upgrading in a production environment. You can use [Velero](https://velero.io/) to implement backup and migrate Kubernetes resources and persistent volumes.
|
||||
|
|
@ -31,8 +33,8 @@ There are some significant API changes in Kubernetes 1.16.x compared with prior
|
|||
|
||||
## How
|
||||
|
||||
A brand-new installer [KubeKey](https://github.com/kubesphere/kubekey) is introduced in KubeSphere v3.0.0, with which you can install or upgrade Kubernetes and KubeSphere. More details about upgrading with [KubeKey](https://github.com/kubesphere/kubekey) will be covered in [Upgrade with KubeKey](../upgrade-with-kubekey/).
|
||||
A brand-new installer [KubeKey](https://github.com/kubesphere/kubekey) is introduced in KubeSphere v3.0.0, with which you can install or upgrade Kubernetes and KubeSphere. More details about upgrading with KubeKey will be covered in [Upgrade with KubeKey](../upgrade-with-kubekey/).
|
||||
|
||||
## KubeKey or ks-installer?
|
||||
## KubeKey or ks-installer
|
||||
|
||||
[ks-installer](https://github.com/kubesphere/ks-installer/tree/master) was the main installation tool as of KubeSphere v2. For users whose Kubernetes clusters were NOT deployed via [KubeSphere Installer](https://v2-1.docs.kubesphere.io/docs/installation/all-in-one/#step-2-download-installer-package), they should choose ks-installer to upgrade KubeSphere. For example, if your Kubernetes is hosted by cloud vendors or self provisioned, please refer to [Upgrade with ks-installer](../upgrade-with-ks-installer).
|
||||
|
|
|
|||
|
|
@ -13,15 +13,15 @@ ks-installer is recommended for users whose Kubernetes clusters were not set up
|
|||
|
||||
- You need to have a KubeSphere cluster running version 2.1.1.
|
||||
|
||||
{{< notice warning >}}
|
||||
{{< notice warning >}}
|
||||
If your KubeSphere version is v2.1.0 or earlier, please upgrade to v2.1.1 first.
|
||||
{{</ notice >}}
|
||||
{{</ notice >}}
|
||||
|
||||
- Make sure you read [Release Notes For 3.0.0](../../release/release-v300/) carefully.
|
||||
|
||||
{{< notice warning >}}
|
||||
{{< notice warning >}}
|
||||
In v3.0.0, KubeSphere refactors many of its components such as Fluent Bit Operator and IAM. Make sure you back up any important components in case you heavily customized them but not from console.
|
||||
{{</ notice >}}
|
||||
{{</ notice >}}
|
||||
|
||||
## Step 1: Download YAML files
|
||||
|
||||
|
|
@ -47,4 +47,4 @@ kubectl apply -f kubesphere-installer.yaml
|
|||
|
||||
```bash
|
||||
kubectl apply -f cluster-configuration.yaml
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -12,11 +12,9 @@ KubeKey is recommended for users whose KubeSphere and Kubernetes were both deplo
|
|||
|
||||
- You need to have a KubeSphere cluster running version 2.1.1.
|
||||
|
||||
{{< notice warning >}}
|
||||
|
||||
{{< notice warning >}}
|
||||
If your KubeSphere version is v2.1.0 or earlier, please upgrade to v2.1.1 first.
|
||||
|
||||
{{</ notice >}}
|
||||
{{</ notice >}}
|
||||
|
||||
- Download KubeKey.
|
||||
|
||||
|
|
@ -31,7 +29,6 @@ wget https://github.com/kubesphere/kubekey/releases/download/v1.0.0/kubekey-v1.0
|
|||
```
|
||||
|
||||
{{</ tab >}}
|
||||
|
||||
{{< tab "For users with poor network connections to GitHub" >}}
|
||||
|
||||
Download KubeKey using the following command:
|
||||
|
|
@ -39,8 +36,8 @@ Download KubeKey using the following command:
|
|||
```bash
|
||||
wget -c https://kubesphere.io/download/kubekey-v1.0.0-linux-amd64.tar.gz -O - | tar -xz
|
||||
```
|
||||
{{</ tab >}}
|
||||
|
||||
{{</ tab >}}
|
||||
{{</ tabs >}}
|
||||
|
||||
Make `kk` executable:
|
||||
|
|
@ -51,15 +48,12 @@ chmod +x kk
|
|||
|
||||
- Make sure you read [Release Notes For 3.0.0](../../release/release-v300/) carefully.
|
||||
|
||||
{{< notice warning >}}
|
||||
|
||||
{{< notice warning >}}
|
||||
In v3.0.0, KubeSphere refactors many of its components such as Fluent Bit Operator and IAM. Make sure you back up any important components in case you heavily customized them but not from console.
|
||||
|
||||
{{</ notice >}}
|
||||
{{</ notice >}}
|
||||
|
||||
- Make your upgrade plan. Two upgrading scenarios are documented below.
|
||||
|
||||
|
||||
## Upgrade KubeSphere and Kubernetes
|
||||
|
||||
Upgrading steps are different for single-node clusters (all-in-one) and multi-node clusters.
|
||||
|
|
|
|||
Loading…
Reference in New Issue