goharbor/harbor-helm

• hightopics#1

  Add relevant topics to the repository

  原因：

  复制粘贴的修复

  复制

  helm-chart, harbor, container-registry, kubernetes, devops, cloud-native, image-registry, private-registry

  待办完成忽略
• highreadme#2

  Reposition README opening to emphasize official deployment of a container registry

  原因：

  当前

  # Helm Chart for Harbor
  
  **Notes:** The master branch is in heavy development, please use the other stable versions instead. A highly available solution for Harbor based on chart can be found [here](docs/High%20Availability.md). And refer to the [guide](docs/Upgrade.md) to upgrade the existing deployment.
  
  This repository, including the issues, focuses on deploying Harbor chart via helm. For functionality issues or Harbor questions, please open issues on goharbor/harbor
  
  ## Introduction
  
  This Helm chart installs Harbor in a Kubernetes cluster.

  复制粘贴的修复

  复制

  # Official Helm Chart for Harbor: Deploy the Cloud-Native Container Registry on Kubernetes
  
  This repository provides the official Helm chart for deploying Harbor, an open-source, enterprise-grade container image registry, into your Kubernetes cluster. It focuses on the deployment and management of Harbor via Helm. For functionality issues or Harbor questions related to Harbor itself, please open issues on goharbor/harbor.
  
  **Notes:** The master branch is in heavy development, please use the other stable versions instead. A highly available solution for Harbor based on chart can be found [here](docs/High%20Availability.md). And refer to the [guide](docs/Upgrade.md) to upgrade the existing deployment.

  待办完成忽略
• mediumfaq#3

  Add an FAQ section clarifying the relationship with the main Harbor project

  原因：

  复制粘贴的修复

  复制

  ## FAQ
  
  ### What is the relationship between goharbor/harbor-helm and goharbor/harbor?
  
  This repository, goharbor/harbor-helm, provides the official Helm chart for deploying the Harbor container registry. The goharbor/harbor repository is where the core Harbor project code resides, and it's the place to open issues for Harbor functionality or questions about the registry itself. This chart focuses solely on the deployment and management of Harbor within a Kubernetes environment.

  待办完成忽略

本次扫描解析到的品类 GEO 通道：google/gemini-2.5-flash, deepseek/deepseek-v4-flash

• 品类问题

  How can I deploy a private container image registry in my Kubernetes cluster?

  你：未被推荐
  AI 推荐顺序：

  1. Harbor (goharbor/harbor)
  2. Docker Registry (distribution/distribution)
  3. Quay.io
  4. GitLab Container Registry (gitlab-org/gitlab)
  5. Nexus Repository Manager (sonatype/nexus-public)

  AI 推荐了 5 个替代方案，却始终没点名 goharbor/harbor-helm。这就是要补上的差距。

  查看 AI 完整回答
• 品类问题

  What Helm chart options exist for installing a secure, production-ready container image repository?

  你：未被推荐
  AI 推荐顺序：

  1. Harbor
  2. Sonatype Nexus Repository Manager
  3. Quay
  4. ChartMuseum
  5. MinIO

  AI 推荐了 5 个替代方案，却始终没点名 goharbor/harbor-helm。这就是要补上的差距。

  查看 AI 完整回答

• Metadata completeness

  warn

  建议：

• README presence

  pass

• Compared to common alternatives in this category, what is the core differentiator of goharbor/harbor-helm?

  pass
  ✓AI 明确点名了 goharbor/harbor-helm

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？

• If a team adopts goharbor/harbor-helm in production, what risks or prerequisites should they evaluate first?

  pass
  ✓AI 明确点名了 goharbor/harbor-helm

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？

• In one sentence, what problem does the repo goharbor/harbor-helm solve, and who is the primary audience?

  pass
  ✓AI 明确点名了 goharbor/harbor-helm

  AI 的回答可能信誓旦旦却是错的。请按事实核对：技术栈、目标人群、差异化点是不是和你实际的对得上？