Description

We encountered the issue in #2697 as well due to us using a different namespace for the operator.
The current chart will always use .Release.namespace which ends up being trivy-system even if the namespace is not being used by any other component.

Looks like this is the only place that .Release.namespace was incorrectly used and appeared after #2646 and this fix should make it consistent with the rest of the chart.

This format for the namespace matches the format for the following now:

• trivy-operator/deploy/helm/templates/secrets/operator.yaml

  Line 7 in f74e994

  namespace: {{ include "trivy-operator.namespace" . }}

• trivy-operator/deploy/helm/templates/deployment.yaml

  Line 5 in f74e994

  namespace: {{ include "trivy-operator.namespace" . }}

• trivy-operator/deploy/helm/templates/serviceaccount.yaml

  Line 6 in f74e994

  namespace: {{ include "trivy-operator.namespace" . }}

• trivy-operator/deploy/helm/templates/secrets/operator.yaml

  Line 7 in f74e994

  namespace: {{ include "trivy-operator.namespace" . }}

• And so on...

Related issues

• Closes bug: Alternate Report Storage PVC namespace is incorrectly configured #2697

Checklist

• I've read the guidelines for contributing to this repository.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).