1. Release Notes
    1. Release Notes - 2.0.2Latest
    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. Intruction
      1. Intro
      2. Port Requirements
    1. Install on Linux
      1. All-in-One Installation
      2. Multi-Node Installation
      3. Installing HA Master and Etcd Cluster
      4. Storage Configuration Instruction
    1. Install on Kubernetes
      1. Prerequisites
      2. Online Installation
      3. Offline Installation
    1. Related Tools
      1. Integrating Harbor Registry
    1. Cluster Operation
      1. Adding New Nodes
      2. High Risk Operation
      3. Uninstalling KubeSphere
  1. Quick Start
    1. Getting Started with Multitenancy
    1. Exposing your APP using Ingress
    1. Deploying a MySQL Application
    1. Deploying a Wordpress Website
    1. Job to compute π to 2000 places
    1. Deploying Grafana using APP Template
    1. Creating Horizontal Pod Autoscaler
    1. S2i: Publish your app without Dockerfile
    1. Canary Release of Microservice APP
    1. CI/CD based on Spring Boot Project
    1. Building a Pipeline in a Graphical Panel
    1. CI/CD based on GitLab and Harbor
    1. Ingress-Nginx for Grayscale Release
  1. Cluster Admin Guide
    1. Multi-tenant Management
      1. Overview of Multi-tenant Management
      2. Overview of Role Management
    1. Platform Management
      1. Account Management
      2. Platform Roles Management
    1. Infrastructure
      1. Service Components
      2. Nodes
      3. Storage Classes
    1. Monitoring Center
      1. Physical Resources
      2. Application Resources
    1. Application Repository
    1. Jenkins System Settings
  1. User Guide
    1. Application Template
    1. Workloads
      1. Deployments
      2. StatefulSets
      3. DaemonSets
      4. Jobs
      5. CronJobs
    1. Storage
      1. Volumes
    1. Network & Services
      1. Services
      2. Routes
    1. Configuration Center
      1. Secret
      2. ConfigMap
      3. Image Registry
    1. Project Settings
      1. Basic Information
      2. Member Roles
      3. Project Members
      4. Internet Access
    1. DevOps Project
      1. DevOps Project Management
      2. DevOps Project Management
      3. DevOps Project Management
      4. DevOps Project Management
      5. DevOps Project Management
  1. Development Guide
    1. Preparing the Development Environment
    1. Development Workflow
  1. API Documentation
    1. API Guide
    1. How to invoke KubeSphere API
KubeSphere®️ 2020 All Rights Reserved.

Storage Classes

The Storage Class is allow to be configured by the cluster admin and provide to users by type and parameter settings. Storage classes are usually created before storage volumes are created. Currently supported storage classes include following 6 types:

Note that if there are multiple storage classes in the system, only one can be set as the default storage class.

Create a Storage Class

Firstly sign in with cluster admin, select Platform → Infrastructure → Storage Classes, then enter into the storage classes panel. As a cluster-admin, you can view all of storage classes and details.


Step 1: Fill In the Basic Information

In the storage classes list, click Create and fill in the basic information:

  • Name: a concise name for the storage class, easy for users to browse and search.
  • Description information: describes the features of storage class in detail. When users want to know more about the storage class, the integrity of description content will become particularly important.
  • Allow volume expansion: the switch of the volume is allowed to expand or not.
  • Reclaim Policy: for volume plugins that support the Delete reclaim policy, deletion removes both the PersistentVolume object from Kubernetes, as well as the associated storage asset in the external infrastructure.

storage class basic information

Step 2: Storage Class Settings

For example, for setting up QingCloud block storage plugin CSI-QingCloud, the parameters for other storage classes are explained in Storage Configuration Instructions.

storage class parameter setting

  • Provisioner: essentially a storage allocator for deciding which volume plug-in to use for PV allocation, such as csi-qingcloud, Ceph RBD, or GlusterFS.
  • Access Modes: specifies the Access Modes of PV, each of which has its own Modes of Access that describe specific functionality. Note that a volume can only be mounted with one access mode at a time, even if it supports multiple access modes.

    • ReadWriteOnce - this volume can be mounted by a single node in read/write mode.
    • ReadOnlyMany - this volume can be mounted by multiple nodes in read-only mode.
    • ReadWriteMany - this volume can be mounted by multiple nodes in read/write mode.
  • type: The type of volume in QingCloud IaaS platform. In QingCloud public cloud platform, 0 represents high performance volume. 3 respresents super high performance volume. 1 or 2 represents high capacity volume depending on cluster‘s zone. 5 represents enterprise distributed SAN (NeonSAN) volume. 100 represents basic volume. 200 represents SSD enterprise volume. See QingCloud Docs for details.
  • maxSize, minSize: Limit the range of volume size in GiB.
  • stepSize: Set the increment of volumes size in GiB.
  • fsType: ext3, ext4, xfs. Default ext4.
  • replica: 1 means single replica, 2 means multiple replicas. Default 2.

Set the Default Storage Class

Only one default storage class is allowed set in a KubeSphere. Click into one of the storage classes, and choose More → Set as default storage class. If you need to delete the storage class, it's obviously to see.

setting default storage class