After seeing some good reasons to consider using Harbor as a container artifact repository around business, security, operational control, and extensibility, let’s learn what Harbor is made up of. In this section, we will learn about the internal components and functions of Harbor. Being a container registry to serve the cloud-native community, Harbor itself is a cloud-native application comprised of multiple smaller microservices performing different activities. Let’s understand how they work together by providing an architectural overview of Harbor.
- Consumers: Consist of all clients and client interfaces
- Fundamental Services: Consist of all core functionalities that are part of the Harbor project and other key third-party projects that are essential components of the overall...