Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALERT-3312 - Adding volumeMounts option to postgres in values #2650

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

psimms-cs
Copy link

@psimms-cs psimms-cs commented Feb 4, 2025

Pull Request template

Link to github issue (if applicable):

ALERT-3312
https://documentation.blackduck.com/bundle/alert/page/topics/troubleshooting/troubleshooting-issues-in-alert.html
Helm Deployment Storage Configuration Issue

"To workaround this issue you must update the postgres.yaml file under helm/blackduck-alert/templates/postgres.yaml.Update the following sections."

If nothing above, what is your reason for this pull request:

Allows to pass in config update to the postgres volumeMount using helm instead of having to patch the postgres.yaml file

Can do this update in values if require to use subPath

  volumeMounts:
    - mountPath: /var/lib/postgresql
      subPath: data
      name: alert-postgres-data-volume

This makes doing this update much easier and not needing to either patch or fork your helm chart to do this update in an automated fashion
*

Changes proposed in this pull request:

deployment/helm/blackduck-alert/templates/postgres.yaml
Add range so can loop over provided volumeMounts from values, this also allows if we require multiple mounts in future
Support for with or without subPath

deployment/helm/blackduck-alert/values.yaml
Adding default behaviour of mount without subpath
*
*
*

Testing

  • Tested helm deployment with default behaviour - Saw expected volumeMounts: in postgres deployment
  • Tested helm deployment with updated values - Saw expected volumeMounts: in postgres deployment
  • Helm lint passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant