-
Notifications
You must be signed in to change notification settings - Fork 431
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
[e2e] cluster should have healthy time synchronization #705
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Comments
/help |
k8s-ci-robot
added
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
Jun 12, 2020
3 tasks
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Oct 8, 2020
/assign |
3 tasks
/remove-help |
k8s-ci-robot
removed
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
Oct 28, 2020
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Describe the solution you'd like
An e2e test to validate machines in the workload cluster have healthy time synchronization
test from aks-engine: https://github.com/Azure/aks-engine/blob/master/test/e2e/kubernetes/kubernetes_test.go#L2207
also related to this PR in image-builder: kubernetes-sigs/image-builder#240
The text was updated successfully, but these errors were encountered: