Ziming

I have the same problem, so this is the dead path right? But why travis can post back comment?

@wangcanfengxs can you take a look whether we can support other ingress providers

we can specify ingress controller, using nginx/contour. What special usercase do you want ?

we can investigate whether this ingress can be optional

not reproduced. Are you sure you input the correct password `Harbor12345`

are you using openshift that facing 'rbac and finalizers' refer issue #758

@holyhope how about this going now ?

hi, we don't hav openshift to test yet, but it should just be same as other k8s cluster. - kubectl apply -f https://raw.githubusercontent.com/goharbor/harbor-operator/v1.3.0/manifests/cluster/deployment.yaml - wget https://raw.githubusercontent.com/goharbor/harbor-operator/v1.3.0/manifests/samples/full_stack.yaml - edit hostname in...

there is no harbor.yml in harbor-operator, not quite understand what you mean. usually we meet similar problem, is because s3 can't be connected directly from the pod, like dns issue,...

yes, this should be changed, but it may break upgrading. do you have any idea, or maybe just document?