Harbor vs Kubernetes

Need advice about which tool to choose?Ask the StackShare community!

Harbor

181
178
+ 1
11
Kubernetes

58.2K
50.4K
+ 1
677
Add tool

Harbor vs Kubernetes: What are the differences?

Introduction:

Harbor and Kubernetes are both open-source containerization platforms that serve different purposes. Harbor is a container image registry, while Kubernetes is a container orchestration platform. Understanding the key differences between these two technologies is essential for organizations to effectively manage containers and streamline their containerization strategies.

  1. Integration with container runtimes: Harbor primarily focuses on managing container images, whereas Kubernetes is designed to orchestrate containerized applications. Harbor integrates with container runtimes like Docker and containerd to store and distribute container images securely. On the other hand, Kubernetes manages the deployment, scaling, and monitoring of containers across a cluster of nodes, ensuring the availability and efficient utilization of resources.

  2. Functionality: Harbor provides features like image scanning, vulnerability assessment, and access control policies to ensure the security of container images. It allows users to push, pull, and manage images with versioning and replication capabilities. Kubernetes, on the other hand, offers functionalities like automatic scaling, load balancing, service discovery, and rolling updates to ensure high availability and resilience of containerized applications.

  3. Scope of operations: Harbor is a container registry, primarily used for storing and distributing container images within an organization. It serves as a centralized repository where developers can push, pull, and manage container images. Kubernetes, on the other hand, goes beyond just storing container images. It manages the entire lifecycle of containerized applications, handling deployment, scaling, monitoring, and orchestration of containers across a cluster.

  4. Level of abstraction: Harbor operates at a lower level of abstraction compared to Kubernetes. It deals with container images and focuses on image management, security, and access control. Kubernetes, on the other hand, operates at a higher level of abstraction, handling the deployment and management of applications composed of multiple containers. It provides abstractions like pods, services, and deployments to simplify the container management process.

  5. User base and community support: Kubernetes has a larger user base and an extensive open-source community supporting its development and maintenance. It is widely adopted by organizations for their container orchestration needs and enjoys continuous improvements and contributions from the community. Harbor, while also having an active community, has a smaller user base as it serves a specific purpose as a container registry.

  6. Adoptability across platforms: Kubernetes is a platform-agnostic container orchestration platform. It can run on various cloud providers, on-premises data centers, and even edge devices. It provides a consistent and standardized way to manage containers across different environments. Harbor, on the other hand, can be used with Kubernetes as its container registry, making it compatible with Kubernetes deployments, but it is not limited to Kubernetes and can be utilized with other container orchestrators as well.

In summary, Harbor is a container image registry focused on securing and distributing container images, while Kubernetes is a container orchestration platform that manages the deployment, scaling, and monitoring of containerized applications. While Harbor focuses on container images, Kubernetes handles the overall management and orchestration of containers.

Decisions about Harbor and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 8.9M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Harbor
Pros of Kubernetes
  • 4
    Good on-premises container registry
  • 1
    Container Replication
  • 1
    Nice UI
  • 1
    Vulnerability Scanner
  • 1
    Supports LDAP/Active Directory
  • 1
    Supports OIDC
  • 1
    Support multiple authentication methods
  • 1
    Perfect for Teams and Organizations
  • 164
    Leading docker container management solution
  • 128
    Simple and powerful
  • 106
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Cheap
  • 8
    Simple
  • 6
    Self-healing
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Captain of Container Ship
  • 3
    A self healing environment with rich metadata
  • 3
    Runs on azure
  • 3
    Backed by Red Hat
  • 3
    Custom and extensibility
  • 2
    Sfg
  • 2
    Gke
  • 2
    Everything of CaaS
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable

Sign up to add or upvote prosMake informed product decisions

Cons of Harbor
Cons of Kubernetes
    Be the first to leave a con
    • 16
      Steep learning curve
    • 15
      Poor workflow for development
    • 8
      Orchestrates only infrastructure
    • 4
      High resource requirements for on-prem clusters
    • 2
      Too heavy for simple systems
    • 1
      Additional vendor lock-in (Docker)
    • 1
      More moving parts to secure
    • 1
      Additional Technology Overhead

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Harbor?

    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

    What is Kubernetes?

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Harbor?
    What companies use Kubernetes?
    See which teams inside your own company are using Harbor or Kubernetes.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Harbor?
    What tools integrate with Kubernetes?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Kubernetesetcd+2
    2
    1153
    Dec 8 2020 at 5:50PM

    DigitalOcean

    GitHubMySQLPostgreSQL+11
    2
    2352
    PythonDockerKubernetes+7
    3
    1096
    May 21 2020 at 12:02AM

    Rancher Labs

    KubernetesAmazon EC2Grafana+12
    5
    1486
    Apr 16 2020 at 5:34AM

    Rancher Labs

    KubernetesRancher+2
    2
    929
    What are some alternatives to Harbor and Kubernetes?
    Grizzly
    Writing scalable server applications in the Java™ programming language has always been difficult. Before its advent, thread management issues made it impossible for a server to scale to thousands of users. This framework has been designed to help developers to take advantage of the Java™ NIO API.
    Docker Compose
    With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
    Rancher
    Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.
    Docker Swarm
    Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
    Argo
    Argo is an open source container-native workflow engine for getting work done on Kubernetes. Argo is implemented as a Kubernetes CRD (Custom Resource Definition).
    See all alternatives