-
Notifications
You must be signed in to change notification settings - Fork 11
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
Persistent Storage with Existing Claim and other improvments #26
Persistent Storage with Existing Claim and other improvments #26
Conversation
…p version 2.17, Added User, Password ENV, Enterprise License and Organization ENV
I tested different configurations and made corrections and improvements to the helm chart |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few comments on the PR; overall, it looks ok.
I am just not sure about this existing claim, can you clarify why it is critical to have it and how do you leverage this?
Does the current setup claim the same PVC from the previous deployment if you use the same deployment name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added features (in the end):
NodeAffinity
ImagePullSecrets
Version bump to 2.17
Added User, Password ENV
Added Enterprise License and Organization ENV
Probes (Liveliness, readiness, and startup)
@antejavor |
Added features:
Variables used for persistence were changed.
Documentation not yet updated.