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. Logging
    1. Log Query
  1. Developer Guide
    1. Introduction to S2I
    1. Custom S2I Template
  1. API Documentation
    1. API Guide
    1. How to Access KubeSphere API
KubeSphere®️ 2020 All Rights Reserved.

Verify Components Installation

Inspect the Installation Logs

When you enable the KubeSphere pluggable components for an installation, you may want to inspect the logs and verify if the installation is successful or not. If failed you need to know how to resolve it. You can follow the instuctions below for reference.

  1. Inspect the dynamic real-time logs output from the Pod ks-installer.
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f
  1. When the logs show the following result, it means the installation is successful.
#####################################################
###              Welcome to KubeSphere!           ###
#####################################################

Console: http://192.168.0.53:30880
Account: admin
Password: [email protected]

NOTES:
  1. After logging into the console, please check the
     monitoring status of service components in
     the "Cluster Status". If the service is not
     ready, please wait patiently. You can start
     to use when all components are ready.
  2. Please modify the default password after login.

#####################################################
  1. Then you will be able to log in to KubeSphere console, enter into PlatformService Components and check the components status. Generally, each component should be healthy.

Component Services

Verify the Result of Pluggable Components

In addition to viewing the component status on the console, you can also use the web kubectl to confirm whether the pluggable component is successfully installed or not.

General speaking, when all pods of a namespace display Running, and all jobs show Completed, it means the component is successfully installed.

Verify KubeSphere Minimal Installation

By default, KubeSphere Installer will be started with minimal installation. You can check the status of Pods and Jobs in the following three namespaces where all system workloads of KubeSphere are running.

kubectl get pod -n kubesphere-system
kubectl get pod -n kubesphere-monitoring-system
kubectl get pod -n kube-system

Verify KubeSphere Application Store Installation

If you have enabled KubeSphere Application Store, you can verify the status of Pods and Jobs using the following command.

kubectl get pods -n openpitrix-system

Verify KubeSphere DevOps System Installation

If you have enabled KubeSphere DevOps System, you can verify the status of Pods and Jobs using the following command.

kubectl get pods -n kubesphere-devops-system

Verify KubeSphere Logging System Installation

If you have enabled KubeSphere Logging System, you can verify the status of Pods and Jobs using the following command.

kubectl get pods -n kubesphere-logging-system

Verify KubeSphere Service Mesh Installation

If you have enabled KubeSphere Service Mesh (Istio-based), you can verify the status of Pods and Jobs using following command.

kubectl get pods -n istio-system

Verify Metrics-server Installation

If you have enabled Metrics-server, you can verify the status of Pods using the following command.

kubectl get pods -n kube-system | grep metrics-server

How to Restart ks-installer

when you see installation process get stucked, you may need to restart the installation. You can delete the Pod ks-installer or scale it to reinstall.

kubectl delete pod ks-installer-xxxxxx-xxxxx -n kubesphere-system