HarborCoreUnhealthy #

Meaning #

The Harbor container registry core instance has been unhealthy for 5 minutes. This can originate from a database outage, misconfiguration, or resource exhaustion.

Impact #

Users and CI/CD pipelines cannot push or pull container images. Deployments that depend on Harbor-hosted images will fail.

Diagnosis #

Check Harbor core pod status:

kubectl get pods -n goharbor -l component=core

Check Harbor core logs:

kubectl logs -n goharbor -l component=core --tail=100

Check Harbor health endpoint:

curl -s https://<harbor-url>/api/v2.0/health

Check the database the core depends on:

kubectl get pods -n goharbor -l application=spilo
kubectl exec -it $(kubectl get pods -n goharbor -l spilo-role=master -o name) -- patronictl list

Mitigation #

Restart the Harbor core deployment:

kubectl rollout restart deployment -n goharbor -l component=core

If the database is down, refer to the PostgreSQL runbooks for recovery steps.