NOTES: All the functionalities of this project has been merged into the harbor-operator project, please navigate to that project repository for trying Harbor operator. This repository is archived!
Harbor is a CNCF hosted open source trusted cloud native registry project that stores, signs, and scans content.
The project harbor-operator is created to cover both Day1 and Day2 operations of an enterprise-grade Harbor deployment. The harbor-operator extends the usual K8s resources with Harbor-related custom ones. The Kubernetes API can then be used in a declarative way to manage Harbor and ensure its high-availability operation, thanks to the Kubernetes control loop.
This operator aims to build a Kubernetes operator on top of the harbor-operator to deploy and manage a full Harbor service stack including both the harbor service components
and its relevant dependent services such as database(PostgresSQL), Cache(Redis) and default in-cluster storage(minIO) services in a scalable and high-available way. It provides
a solid unified solution to cover the lifecycle management of Harbor service. The customize resource HarborCluster is defined to describe the full harbor stack that includes
the dependencies. The CR HarborCluster owns the underlying CRs like Harbor managed by harbor-operator, Postgresql managed by PostgresSQL operator, RedisFailover managed by Redis
operator and MinIOInstance managed by minIO operator. The reconcile process of HarborCluster wil make sure the actual state of the HarborCluster CR matches the designed state set
in the spec by the users. The reconcile process also takes care of the service creation and ready order to reflect the real service dependent topology to avoid starting failures issues.
Project codebase is scaffolded by kubebuilder V2(.2).
With this operator, you're able to deploy and manage a full Harbor stack:
- Provision a full Harbor stack including the relevant dependent services like database(PostgresSQL), cache(Redis) and in-cluster storage(minIO) services in a scalable and high-available way.
- Inherit deployment customization capabilities from the underlying harbor-operator, the following components could be optional:
- ChartMuseum
- Notary
- Clair
- Trivy
- Update the spec of the deployed Harbor stack to do adjustments like replicas (scalability) and service properties.
- Upgrade the deployed Harbor stack to a newer version.
- Delete the Harbor stack and all the related resources owned by the stack.
Diagram below shows the overall design of this operator,
For more design details, check the architecture document.
You can follow the installation guide to deploy this operator to your K8s clusters.
Additionally, follow sample deployment guide to have a try of deploying the sample to your K8s clusters.
| Component \ Versions | 0.5.0 | 1.0.0 | 1.1.0 |
|---|---|---|---|
| Harbor | 1.10.x | [TBD] | [TBD] |
| harbor-operator | 0.5.2 | [TBD] | [TBD] |
| PostgresSQL operator | 1.5.0 | [TBD] | [TBD] |
| Redis operator | 1.0.0 | [TBD] | [TBD] |
| minIO operator | 3.0.13 | [TBD] | [TBD] |
| Kubernetes / Versions | 0.5.0 | 1.0.0 | 1.1.0 |
|---|---|---|---|
| 1.17 | + | [TBD] | [TBD] |
| 1.18 | + | [TBD] | [TBD] |
| 1.19 | + | [TBD] | [TBD] |
Notes: += verified -= not verified
Interested in contributions? Follow the CONTRIBUTING guide to start on this project. Your contributions will be highly appreciated and creditable.
- Slack channel #harbor-operator-dev at CNCF Workspace
- Send mail to Harbor dev mail group: harbor-dev@lists.cncf.io
See documents here.