-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve MHC e2e tests #3656
Comments
/help |
@fabriziopandini: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
/milestone v0.4.0 |
/area testing |
This work should possible address also testing for KCP remediation |
@fabriziopandini Going to work on this issue, feel free to unassign me if someone is working on it! /assign @tcordeu |
Thank you @tcordeu ! |
Go ahead! /unassign |
/assign |
The current MHC object in E2E tests is specifically configured to always trigger remediation after 30s the node is started.
cluster-api/test/e2e/data/infrastructure-docker/bases/mhc.yaml
Lines 15 to 18 in 0cf9f80
As per comment #3651 (review)
Can we revisit this? I understand the goal here is to make MHC fail and remediate after 30s, but if we could actually flip this to control when this happens and reduce the timeout, that would probably be better?
For example, our tests could be a little bit more controlled if we apply the unhealthy condition, wait for the timeout, and ultimately check that health check or remediation happened.
/kind feature
The text was updated successfully, but these errors were encountered: