Tim Brown
Tim Brown
Hi @unickq, I have managed to work around this locally by updating the style sheet with the following (I added it to the end of mine): ``` :root { /*...
Hi ferventcoder, I know it's a bit early (as 0.9.10 has only just been released) but I was wondering if you have an estimate for when this work might be...
Just wondered if there is any update on when this might be fixed?
Hi @ferventcoder, Is there any update on this? Thanks, Tim
I found you can also fix it using Regular Expressions View Filter:  The key is to look for the Job folder name. This means...
I managed to work around this with an init container, I used the following YAML `./harbor/kustomization.yaml`: ```lang=yaml helmCharts: - name: harbor version: 1.8.1 repo: https://helm.goharbor.io releaseName: deployment-harbor namespace: harbor valuesFile:...
I created a PR but not sure how it will be received 😅 https://github.com/goharbor/harbor-helm/pull/1170
I'm seeing this behaviour too: ``` kubectl api-versions | grep monitoring.coreos.com/v1 monitoring.coreos.com/v1 monitoring.coreos.com/v1alpha1 ``` values.yaml: ``` metrics: enabled: true serviceMonitor: enabled: true ``` In my case I am using customize...
Ok, in my case I think it's that kustomize isn't telling Harbor that that API exists. I will store a local copy and update the chart to remove that check...
Ahh, sorry, didn't think to check there 😳