-
Notifications
You must be signed in to change notification settings - Fork 2k
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
internal/store: fix metrics slice length for init containers #1734
Conversation
|
Welcome @honpey! |
/cc @jan--f |
@honpey: GitHub didn't allow me to request PR reviews from the following users: jan--f. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
lgtm!
@honpey would you mind rebasing your branch against master to make the CI pass? |
In kubernetes#1731, the dynamic slice was introduced to fix potential panic under Spec.Containers scenario, however there may be same panic for Spec.InitContainers scenario. This patch fix it referring to kubernetes#1731 Signed-off-by: honpey <honpey@gmail.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: honpey, jan--f, mrueg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
done |
/lgtm |
In #1731 ,
the dynamic slice was introduced to fix potential panic under
Spec.Containers scenario, however there may be same panic for
Spec.InitContainers.
This patch fix it referring to #1731
What this PR does / why we need it:
fix potential panic when there exists disconnect of
Spec.InitContainers
andStatus.InitContainerStatuses
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #