Ángel
Ángel
I was able to expose the metrics in the port 82 by creating the following file: ```bash # cat /data/nginx/custom/http.conf server { listen 82; location /nginx_status { stub_status; access_log off;...
@knqyf263 Thanks for the awesome description of the behaviour of trivy. Looking forward to seeing how you manage to gather the origin of a Debian package :). Then modify it...
any news here?
I'm having problems also trying to use `replacements` on targets with wildcards: ```yaml replacements: - source: kind: GitRepository fieldPath: metadata.name targets: - select: kind: HelmRelease fieldPaths: - spec.valuesFrom.*.name ```
+1 looking for it! Meanwhile im trying to understand if I can use `service` instead of `ingress` in the `Gslb.spec.resourceRef` attribute. That would help transitioning from ingress to gateway api...
I'll test it in the upcoming days :) (hopefully)
Any chance to recover this PR?
I agree on the feature of modifying the injection label. By default it is `namespace`, and sometimes metrics uses `exported_namespace` among others. Do you want to implement it?
I was thinking about using either `exported_namespace` or `namespace`