v2.1
v2.0
v1.0
  1. Release Notes
    1. Release Notes - 2.1.1Latest
    1. Release Notes - 2.1.0
    1. Release Notes - 2.0.2
    1. Release Notes - 2.0.1
    1. Release Notes - 2.0.0
  1. Introduction
    1. Introduction
    1. Features
    1. Architecture
    1. Advantages
    1. Glossary
  1. Installation
    1. Introduction
      1. Intro
      2. Port Requirements
      3. Kubernetes Cluster Configuration
    1. Install on Linux
      1. All-in-One Installation
      2. Multi-Node Installation
      3. High Availability Configuration
      4. Air Gapped Installation
      5. StorageClass Configuration
      6. Enable All Components
    1. Install on Kubernetes
      1. Prerequisites
      2. Install on K8s
      3. Air Gapped Installation
      4. Install on GKE
    1. Pluggable Components
      1. Pluggable Components
      2. Enable Application Store
      3. Enable DevOps System
      4. Enable Logging System
      5. Enable Service Mesh
      6. Enable Alerting and Notification
      7. Enable Metrics-server for HPA
      8. Verify Components Installation
    1. Upgrade
      1. Overview
      2. All-in-One
      3. Multi-node
    1. Third-Party Tools
      1. Configure Harbor
      2. Access Built-in SonarQube and Jenkins
      3. Enable built-in Grafana Installation
      4. Load Balancer plugin in Bare Metal - Porter
    1. Authentication Integration
      1. Configure LDAP/AD
    1. Cluster Operations
      1. Add or Cordon Nodes
      2. High Risk Operations
      3. Uninstall KubeSphere
  1. Quick Start
    1. 1. Getting Started with Multi-tenancy
    1. 2. Expose your App Using Ingress
    1. 3. Compose and Deploy Wordpress to K8s
    1. 4. Deploy Grafana Using App Template
    1. 5. Job to Compute π to 2000 Places
    1. 6. Create Horizontal Pod Autoscaler
    1. 7. S2I: Publish your App without Dockerfile
    1. 8. B2I: Publish Artifacts to Kubernete
    1. 9. CI/CD based on Spring Boot Project
    1. 10. Jenkinsfile-free Pipeline with Graphical Editing Panel
    1. 11. Canary Release of Bookinfo App
    1. 12. Canary Release based on Ingress-Nginx
    1. 13. Application Store
  1. DevOps
    1. Pipeline
    1. Create SonarQube Token
    1. Credentials
    1. Set CI Node for Dependency Cache
    1. Set Email Server for KubeSphere Pipeline
  1. User Guide
    1. Configration Center
      1. Secrets
      2. ConfigMap
      3. Configure Image Registry
  1. Logging
    1. Log Query
  1. Developer Guide
    1. Introduction to S2I
    1. Custom S2I Template
  1. API Documentation
    1. API Documentation
    1. How to Access KubeSphere API
  1. Troubleshooting
    1. Troubleshooting Guide for Installation
  1. FAQ
    1. Telemetry
KubeSphere®️ 2020 All Rights Reserved.

Documentation

简体中文English

Upgrade All-in-One

Edit

Prerequisite

You need to download Installer 2.1.1, please refer to Upgrade Overview.

Step 1: Sync Configuration

Installer will read the files under conf directory when upgrade. Thus you need to sync the changes from the conf directory from the old version to 2.1.1 before upgrading, including two scenarios as follows.

Upgrade from 2.0.x

  1. You need to determine if the parameters configuration has been changed in conf/vars.yaml. If any parameters were changed, then sync them to 2.1.1 conf directory accordingly. In particular, the storage class needs to be consistent with the old version.

Note: The configuration file is vars.yaml in 2.0.x. But it changes to common.yaml since 2.1.0, and separates the cloud provider related configurations into several files.

  1. KubeSphere has decoupled some components since 2.1.0 and supports installing optional components according to your needs. The Installer will only upgrade the minimal component by default in common.yaml, you need to change the enabled components settings to true in common.yaml, then execute the upgrade script.

Upgrade from 2.1.0

Same as above, please sync the configuration changes from 2.1.0 conf directory to 2.1.1. And the storage class needs to be consistent with 2.1.0. Please notice that do not copy and overlay the whole files from 2.1.0 to 2.1.1. It may cause some unexpected errors. For example, the Kubernetes version defaults to 1.16.7 instead of 1.15.4 in 2.1.1.

Please notice that if you have enabled any components by editing the ks-installer ConfigMap in 2.1.0, please sync from 2.1.0 to 2.1.1 by manually enabling these components in 2.1.1 common.yaml. The upgrade script will read from common.yaml.

Step 2: Start Upgrade

When you are done, refer to the following steps to upgrade:

  1. Enter scripts directory, execute the upgrade script using root user.
./upgrade.sh
  1. Make sure anything looks correctly, type yes to start upgrade. Please wait patiently. If you see "Successful" returned after completed, it means the installation is successful. You can verify the installation logs using the command as follows.
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath={.items[0].metadata.name}) -f

Finally, use your account and password to log in KubeSphere, click About on the top of right to check the version and verify if upgrade successfully.

If you have further questions please do not hesitate to raise issues on GitHub.

KubeSphere Docs