-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Associate instance group to pod validation failures in cluster validation. #10237
Associate instance group to pod validation failures in cluster validation. #10237
Conversation
Hi @bharath-123. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
@bharath-123: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/cc @johngmyers |
I believe that failures of pods of priorityClass "system-cluster-critical" are cluster-wide, so should not be marked as specific to their pod's instanceGroup. Failures of pods of priorityClass "system-node-critical" are specific to the node, so should be marked as specific to their pods instanceGroup. |
/ok-to-test |
Yes your right. Will take care of this. Thanks for pointing this out! |
…stance group In the ValidationError struct, there is a field to identify the instance group to which the ValidationError is associated with. For pod related ValidationErrors, it is not straightforward to identify the instance group to which the pod is associated with. To acheive this, we create a node to instance group mapping in ValidateNodes. This node to instance group mapping is used in collectPodFailures to identify the pod instance group by using the pod's hostIp field. We don't associate system-cluster-critical pods to instance groups as those pod failures are cluster wide
We are now able to identify the instance group associated with a pod. Add an extra layer to the validatePodFailure to the test where we create a mock InstanceGroup and associate the pod failures with the instance group to which the pod belongs to.
Now that we are able to associate pod validation failures with the instance groups. We can remove the TODO comment
e9cf06d
to
208199b
Compare
/retest |
Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bharath-123, johngmyers 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 |
This PR fixes #10183