Skip to content

Deploying the Alternate Report Storage with Helm create a PVC forced in trivy-system namespace #2615

@bprieur

Description

@bprieur

What steps did you take and what happened:

Deploying with Helm in a namespace other than trivy-system results in the PVC being created in the trivy-system namespace.

What did you expect to happen:

The PVC should be deployed into the specified namespace.

To achieve this, modify the PVC template in the Helm charts by removing the namespace setting, allowing it to be set dynamically.

Environment:

  • Trivy-Operator version (use trivy-operator version): 0.29.0
  • Kubernetes version (use kubectl version): v1.29.14+7cf4c05
  • OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): CoreOS

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions