Skip to content

Init container configuration through values.yaml is ignored #820

@malexmave

Description

@malexmave

🐞 Bug report

When implementing init containers, I added the configuration to the values.yaml files, but didn't actually pull it into the ScanSpec, so at the moment, it will do nothing. I'll either have to update the ScanSpec for all scanners to incorporate the initContainer information, or remove it from the values.yaml because there are very few cases where it is actually a good idea to configure them here.

While doing so, I should also check if there are other things that can be configured using the values.yaml but that are not actually put into the ScanSpec / ParseDefinition afterwards.

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