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

[prometheus] fix: Add apiVersion and kind to STS persistent volume claim #4610

Merged
merged 3 commits into from
Jun 19, 2024

Conversation

grzesuav
Copy link
Contributor

@grzesuav grzesuav commented Jun 18, 2024

What this PR does / why we need it

Add explicitly persistentVolumeClaim API version and kind - they are added by API server which causes a drift in argo cd state - and having them do not make any charm.

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

API version and kind is added by API server which causes a drift in argo cd state

Signed-off-by: Grzegorz Głąb <[email protected]>
@grzesuav
Copy link
Contributor Author

This is what I see in argocd, adding the missing field would resolve this and it is not doing any charm

image

@grzesuav grzesuav changed the title fix: Add apiVersion and kind to STS persistent volume claim [prometheus] fix: Add apiVersion and kind to STS persistent volume claim Jun 18, 2024
@grzesuav
Copy link
Contributor Author

@gianrubio @naseemkullah @Xtigyro @zanhsieh @zeritti can you take a look ?

Copy link
Member

@zeritti zeritti left a comment

Choose a reason for hiding this comment

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

Thank you, @grzesuav, for your PR, LGTM.

@zeritti zeritti merged commit 4fb48ee into prometheus-community:main Jun 19, 2024
4 checks passed
@grzesuav grzesuav deleted the patch-1 branch June 19, 2024 19:41
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