Johan Abbors

A better solution would be to just exclude the nginx deployment and use the workaround in https://github.com/goharbor/harbor/issues/11906.

We experienced the same error after upgrading from 2.2.x to 2.4.11. In our case we had patched the deployment with the below patch. After removing it, the error disappeared and...

Which version of harbor did you try with? I managed to get harbor 1.10.2 working with Istio using config I posted in https://github.com/goharbor/harbor-helm/issues/77. Not using the chartmusem so don't know...

@Morriz, no I did not. I analysed the `core` source code but couldn't find anything indicating that a request towards `/v2/` would trigger any read/writes in the database. It's just...

We migrated our harbor instance to k8s around the 1.10 release and have been running the 1.10.x releases with Istio for some while. No nginx deployed and the Istio virtual...

Thanks @heilerich for you patches. I deployed harbor with helm (chart version 1.7.5) with Istio mTLS enabled and it worked right away. Just to be extra clear, the helm chart...

@Morriz Nice, did you have any troubles with trivy image scnanning? At least for us trivy installs just fine, but but during a scan job it fails to pull the...

@Morriz Are you able to share the VirtualService resources that you create? Or guide me where I can see them? I took a look at the otomo-core source code but...

Thanks, was able to render the resources and compare them with our VirtualService. They looked mostly the same as the one posted by the author of this issue, which is...

@ChrisJBurns with Helm chart are you referring to? The one I extracted from otomi-core or the official chart which is the one I'm trying to get working.