Harbor vs Flux CD: What are the differences?
Harbor: Manage and serve container images in a secure environment (created at VMware). Harbor is an open source cloud native registry that stores, signs, and scans container images for vulnerabilities Harbor solves common challenges by delivering trust, compliance, performance, and interoperability. It fills a gap for organ; Flux CD: The GitOps operator for Kubernetes. It is a tool that automatically ensures that the state of your Kubernetes cluster matches the configuration you’ve supplied in Git. It uses an operator in the cluster to trigger deployments inside Kubernetes, which means that you don’t need a separate continuous delivery tool.
Harbor and Flux CD are primarily classified as "Docker Registry" and "Container" tools respectively.
Some of the features offered by Harbor are:
- Multi-tenant content signing and validation
- Image replication between instances
- Extensible API and graphical UI
On the other hand, Flux CD provides the following key features:
- Describe the entire desired state of your system in Git. This includes apps, configuration, dashboards, monitoring, and everything else
- Use YAML to enforce conformance to the declared system. You don’t need to run kubectl because all changes go through Git. Use diffing tools to detect divergence between observed and desired state and receive notifications
- Everything is controlled through pull requests, which means no learning curve for new developers. Just use your standard PR process. Your Git history provides a sequence of transactions, allowing you to recover system state from any snapshot. Fix a production issue via pull request rather than making changes to the running system
Harbor is an open source tool with 11.5K GitHub stars and 3.13K GitHub forks. Here's a link to Harbor's open source repository on GitHub.