Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

kubelet e2e: Enable the disruptive test #1012

Merged
merged 2 commits into from
Sep 28, 2020

Conversation

surajssd
Copy link
Member

The test was disabled because the runc issue rendered the nodes
unusable,now that it is fixed in flatcar stable it makes sense to enable
it.

Fixes #1002

@invidian
Copy link
Member

It seems self-hosted kubelet does not pick up the labels properly?

    kubelet_disruptive_test.go:72: label "testing.io":"yes" not found on node "ip-10-0-15-45"
    kubelet_disruptive_test.go:72: label "roleofnode":"testing" not found on node "ip-10-0-15-45"

The test was disabled because the runc issue rendered the nodes
unusable,now that it is fixed in flatcar stable it makes sense to enable
it.

Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
This commit adds the labels that the worker pool is missing.

Signed-off-by: Suraj Deshmukh <suraj@kinvolk.io>
@surajssd surajssd force-pushed the surajssd/enable-kubelet-e2etest branch from 006d4cc to 1123440 Compare September 28, 2020 10:34
@surajssd
Copy link
Member Author

@invidian PTAL. Fixed the issue with test failing on AWS.

@surajssd surajssd merged commit d756605 into master Sep 28, 2020
@surajssd surajssd deleted the surajssd/enable-kubelet-e2etest branch September 28, 2020 11:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable e2e test case TestSelfHostedKubeletLabels
2 participants