Skip to content
This repository has been archived by the owner on May 13, 2021. It is now read-only.

Latest commit

 

History

History
31 lines (21 loc) · 1.39 KB

architecture.md

File metadata and controls

31 lines (21 loc) · 1.39 KB

Harbor cluster operator design

Overview

The overall design of the operator is shown below:

harbor-cluster-operator

  • A top CR(Customize Resource) harbor-cluster is defined to represent the full harbor stack. It is governed by the corresponding controller.
  • The harbor service components are created and managed through the harbor operator and the CR harbor.
  • The following related CRs of the dependent services will be created and managed by their operator controllers and bound to the Harbor CR via secret or configMaps ways. Sometimes, the configurations of dependencies may be directly populated into the pods of CR Harbor to reduce the difficulties.
    • Database service (PostgresSQL)
    • Cache service (Redis)
    • Storage service (minIO)
  • The dependent CRs are owned by the harbor-cluster CR to enable the cascaded deletion and GC when the CR harbor-cluster is deleted.

CRD

This document explains the various fields supported in spec of CR harbor-cluster and how to use these fields to deploy harbor cluster.

Reconcile flow

Read reconcile flow document to learn the overall flow.

Misc

[TBD]