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.

Application Repository

KubeSphere built the application repository service based on OpenPitrix, which is an open-source application management platform for multi-cloud environment, powered by QingCloud as well. KubeSphere Application Repository supports for Helm application. In the application repository, each application consists of Helm package, which including some manifests and templates.

The application package can be stored into an HTTP/HTTPS server or an S3 object storage. The application repository is an external storage independent of KubeSphere, which can be QingStor object storage or AWS object storage, where the content is the configuration and template files. Once the repository is registered, the stored application packages are automatically indexed into deployable applications.

Add the Application Repository

Sign in with cluster admin, then click Platform Management → App Repository to enter into the list page.

application repo

  1. Click Add App Repository button.

  2. Fill in the basic information of the repository in the pop-up window, and click the Validate button.

Before add the repository into KubeSphere, you have to prepare a backend object storage to store the Helm application package, KubeSphere supports QingStor object storage and AWS S3 object storage.

  • App Repository Name: a concise name for the application repository can help users to browse and search.

  • type: only support Helm Chart.

  • url: supports the following three protocols

    • S3: QingStor Bucket URL is HTTP at the beginning, but can be compatible with the S3 protocol, if URL is matched S3 style s3.<zone-id>.qingstor.com/<bucket-name>/, then QingStor service can use S3 interface.
    • http: support read but not support write, only supported for the application of the repository store (object), support deploy to runtime. For example, http://openpitrix.pek3a.qingstor.com/package/, the application contains three sample repository and will be automatically imported into the platform after added.
    • https: readable, non-writable, supports only retrieving applications from the application repository (object store) and deploying to the runtime.
  • Description: briefly introduce the main features of the application repository, so that users can further understand the application repository;

  • After passing the validation, click OK button to save it. Once you add an application repository, it will automatically loads all the application templates of that repository.

create application repository

Google has two application repositories which includes multiple helm applications. QingStor has made a mirror for the stable one (we will develop a commercial application repository for enterprises bussiness later). Users can add the required application repositories as needed:

  • QingStor Helm Repo: https://helm-chart-repo.pek3a.qingstor.com/kubernetes-charts/
  • Google Stable Helm Repo: https://kubernetes-charts.storage.googleapis.com/
  • Google Incubator Helm Repo: https://kubernetes-charts-incubator.storage.googleapis.com/

In the private cloud scenario within the enterprise, users can build their own application repositories based on Helm specifications, thus can develop and upload the applications that meet the business requirements of the enterprise to their own application repositories, and then complete the distribution and deployment of the applications based on KubeSphere.