Skip to content

Commit 6387f27

Browse files
committed
Update Blog “setting-up-harbor-as-a-local-container-registry-in-hpe-private-cloud-ai”
1 parent a4b3d6c commit 6387f27

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

content/blog/setting-up-harbor-as-a-local-container-registry-in-hpe-private-cloud-ai.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,17 @@
11
---
22
title: Setting up Harbor as a local container registry in HPE Private Cloud AI
3-
date: 2025-06-30T15:31:53.670Z
3+
date: 2025-07-03T07:21:44.007Z
44
author: Guoping Jia
55
authorimage: /img/guoping.png
66
disable: false
7+
tags:
8+
- HPE Private Cloud AI
9+
- Harbor
10+
- Kubernetes
11+
- Container Registry
12+
- DockerHub
13+
- Local Container Registry
14+
- Docker
715
---
816
A container registry serves as a centralized system for storing and managing container images. In today’s fast-paced containerized application development landscape, speed, security and control over container workflows using a robust container registry are critical. While both cloud-based container registries, such as Google Container Registry (*GCR*), Azure Container Registry (*ACR*), and Amazon Elastic Container Registry (*ECR*), and third-party services like *DockerHub*, *GitHub* / *GitLab* Container Registry, and *JFrog* Container Registry, offer convenience, organizations often face challenges with latency, external dependencies, and security compliance constraints.
917

0 commit comments

Comments
 (0)