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

server: add option to set policy package PVC name via values #241

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rdimaio
Copy link
Contributor

@rdimaio rdimaio commented Feb 26, 2025

part of #238

@rdimaio rdimaio requested a review from dchristidis February 26, 2025 13:43
@@ -166,6 +166,10 @@ policyPackages:
# - moduleName: vo_2_policy_package
# requirement: git+/~https://github.com/vo-2/vo-2-policy-package@v0.1.0
# version: 0.1.0
# Set true to create a PVC for the policy packages; leave false if providing it separately.
createPvc: false
# If providing the PVC separately, set its name here.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am confused by this comment. ‘If separate, then do this.’ But when not ‘if separate’, don’t you need to set it to something that will be unique to the release?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see how the comment could be misleading. If not separate (i.e. createPvc: true), you'd still set this name to something unique to the release - the comment was mostly to indicate what to do in case you wanted to provide the PVC separately

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.

2 participants