search

goharbor / harbor-cluster-operator

Kubernetes operator for deploying and managing Harbor and its dependent services (database, cache and storage) in a scalable and high-available way
Apache License 2.0
27 stars 14 forks source link

registry pod may failed to start in v0.5.0 #235

Open bitsf opened 4 years ago

bitsf commented 4 years ago

In v0.5.0 there's a known issue that sometimes when deploy harbor, that pod sz-harbor-cluster-harbor-registry-68974d455d-27c5t container registry may failed to start, and in log it will report parse /etc/registry/config.yaml failed or not found. The workaround is delete and redeploy harbor, it usually will be success.

An issue also tracked in repo harbor-operator https://github.com/goharbor/harbor-operator/issues/85