blackducksoftware
add possibility to set initContainer resources
This allows the blackduck helm chart to be deployed, even if the cluster requires committed resources on all components.
These changes look to be under the container section. There are existing vars to inject resources for these sections per service.
thanks @skatzman-synopsys for taking a look. It is correct, that resources can be set for most containers. But not for initContainers. We must set resources also in the initContainers to be able to deploy. Therefore the PR.
@skatzman-synopsys if there is a possibility to set resources in all initContainers, I am still too happy to learn how to do it. Do you have a sample values.yaml that would show me how to set them?
2022-02-15: Information from Synopsys correlating to this PR: This enhancement has been dispositioned and assigned a status of "Plan of Intent". Here is what this means: Plan of Intent: The issue has been reviewed and is being considered for a release within the next six (6) months, but a version has not been assigned.
In our CI/CD environment we have resourcequota set on all namespaces. Since initContainer resources cannot be set, replicaSets won't be able to start the pods. Workaround is to delete the resource quota but that's not desirable.
Please approve the PR.
closing this PR, because it has been resolved in the meantime. Besides datadog java initContainer (which is disabled per default), all resources can be defined in the actual helm chart releases.