Open wangchao732 opened 1 day ago
For me, it was an issue with the ingress.
Check if /api
, /service
, /v2
, /chartrepo
and /c
all point to the harbor-core
service, instead of the harbor-portal
service.
- match: Host(`YOUR_HARBOR_URL_HERE`)
kind: Rule
services:
- name: harbor-portal
namespace: harbor
port: 80
- match: Host(`YOUR_HARBOR_URL_HERE`) && PathRegexp(`^/(api|service|v2|chartrepo|c)/`)
kind: Rule
services:
- name: harbor-core
namespace: harbor
port: 80
Note: I am using traefiks ingressroute. you probably have to change it for your ingress controller.
@another-novelty Thank you for your reply! I didn't find any issues with the configuration.And attempt to modify the admin password in PLSQL, it is still the same.
I have not used Ingress. nodeport access.
@another-novelty
helm install harbor . --namespace harbor --create-namespace Error: INSTALLATION FAILED: template: harbor/templates/registry/registry-secret.yaml:11:62: executing "harbor/templates/registry/registry-secret.yaml" at <include "harbor.secretKeyHelper" (dict "key" "REGISTRY_HTTP_SECRET" "data" $existingSecret.data)>: error calling include: template: harbor/templates/_helpers.tpl:59:41: executing "harbor.secretKeyHelper" at <.data>: wrong type for value; expected map[string]interface {}; got interface {}
harbor registry all v2.11.1
setup:
1、helm upgrade --install harbor harbor/harbor --namespace harbor --create-namespace 2、all server running is health 3、look all server logs not error info
need help ! thanks !