bump kubecost-modeling for cve fixes #3606
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: Cliff Colvin <ccolvin@kubecost.com>
|
/cherry-pick v2.3 |
|
/cherry-pick v2.4 |
nik-kc
approved these changes
Aug 23, 2024
|
Cherry-pick failed with |
gcp-cherry-pick-bot bot
pushed a commit
that referenced
this pull request
Aug 23, 2024
bump kubecost-modeling for cve fixes
Merged
cliffcolvin
added a commit
that referenced
this pull request
Aug 23, 2024
bump kubecost-modeling for cve fixes (cherry-pick #3606)
# for free
to join this conversation on GitHub.
Already have an account?
# 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: Cliff Colvin ccolvin@kubecost.com
What does this PR change?
Bump kubecost-modeling image for cve fixes:
CVE-2024-4603
CVE-2024-5535
CVE-2024-4603
CVE-2024-5535
CVE-2024-6923
CVE-2024-37891
Does this PR rely on any other PRs?
NA
How does this PR impact users? (This is the kind of thing that goes in release notes!)
NA
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?
NA
How was this PR tested?
locally
Have you made an update to documentation? If so, please provide the corresponding PR.
NA