DQ

#578 is caused by a permission issue, in some provisioned it may not compatible with securityContext, you need to fix the permission by yourself

hi is this PR slove the same issue with #980 ?

when using ingress, no service for it is by design, what is you scenario? do you want to using harbor with ingress and istio?

hi @libo-sober , we are not tested harbor with apisix, in our test pipeline only test with nginx ingress. you can try it in your environment.

Hi, what secret value you wanna replace? We also provides `secret` config in `values.yaml`. are those config met your use case?

if you use cert-manager, you can use cert-manager to manage the certs, and refer it on `value.yml`

you can try to manually scale it, we didn't have a plan to support HPA recently.

Hi @JhoLee , thank you for mention this, could you help to commit a PR to add this label to harbor-helm, we already have some similar labels but not follow...

this value only works when you first time installs Harbor.

hi @Vad1mo , because the error is caused by `commonName`, how about just assign an arbitrary name for `expose.tls.auto.commonName` as a workaround? so we can avoid changes a lots of...