update configmap reloader image #2763
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: chipzoller <[email protected]>
jessegoodier
approved these changes
Nov 16, 2023
chipzoller
added a commit
that referenced
this pull request
Nov 16, 2023
Signed-off-by: chipzoller <[email protected]>
2 tasks
jessegoodier
pushed a commit
that referenced
this pull request
Nov 16, 2023
Signed-off-by: chipzoller <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: chipzoller [email protected]
What does this PR change?
Updates the Prometheus ConfigMap reloader image in the EKS values with the one changed in #2698. The same image has been copied to public.ecr.aws/kubecost.
Does this PR rely on any other PRs?
No, is a follow-on fix from #2698
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Allows users to upgrade to 107 in EKS
Links to Issues or tickets this PR addresses or fixes
What risks are associated with merging this PR? What is required to fully test this PR?
Image can't be pulled or upgrade fails.
How was this PR tested?
Pulled image locally
Have you made an update to documentation? If so, please provide the corresponding PR.
See kubecost/docs#816