Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[prometheus] Bump chart dependencies #3422
[prometheus] Bump chart dependencies #3422
Changes from all commits
46362be
b3dd332
c4fb8e1
e5515df
fca1759
24ba4b5
b45f0e6
57b42f6
80c5161
9c0fe72
31d2efe
b7c7e73
a3684b4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@zeritti
do we need to provide some way to tell how to export the user current data and import to the new version?
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.
which data should that be?
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.
@monotek
templates/pvc.yaml, in case the user enable PVC.
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.
@zanhsieh There is no issue related to the pushgateway's data stored in a persistent volume during the upgrade, the volume/its contents are not affected and no change on the pushgateway's side in this respect.
The same is true for Prometheus's PV - no side efects have come up in my tests.
However, whilst upgrading the pushgateway subchart with deployment and persistent volume enabled is straightforward, not so with statefulset and persistent volume - the latter cannot be patched due to changing labels and the upgrade fails. Fo this scenario, I'll have to add a note on upgrading - deleting the pushgateway's statefulset is needed before upgrading.
For prometheus-pushgateway, we should consider whether including the full label set from
prometheus-pushgateway.defaultLabels
(withapp.kubernetes.io/version
) in statefulset'sspec.volmeClaimTemplates
is reasonable as it leads to requiring manual intervention at an upgrade.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.
@zeritti
Thank you for testing that out. I think put some warning text as for pushgateway subchart sts with pvc as you suggested should be fine. We only do due diligence since in that case the user decided to go with sts - that's their choice.