fix: Kubecost Container Version health with EKS 1.25+ #1607
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.
EKS version 1.25+ breaks cost-model container
issue makes pod unhealthy because of error:
ref: tektoncd/pipeline#5128
What does this PR do?
Bumps container tag for cost-model that has the new HPA ApiVersion support with EKS version 1.25+. Without it, container is never in healthy state by kubelet.
Motivation
related to this: tektoncd/pipeline#5128
More
pre-commit run -a
with this PRFor Moderators