Skip to content
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.

Sign up for GitHub

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

Jump to bottom

have e2e jobs that use docker once we move kinder to latest kind #1592

Closed
neolit123 opened this issue Jun 3, 2019 · 5 comments
Closed

have e2e jobs that use docker once we move kinder to latest kind #1592

neolit123 opened this issue Jun 3, 2019 · 5 comments
Assignees
@neolit123 @fabriziopandini
Labels
area/test kind/design Categorizes issue or PR as related to design. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
v1.16

Comments

@neolit123
Copy link
Member

upstream kind has moved to crictl and containerd on the k8s nodes it creates.
given we are using kind/kinder for all tests we need to be able to test docker on k8s nodes too.

currently kinder is not using the latest kind, but once it does we need to think of having docker jobs.
@neolit123 neolit123 added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. area/test kind/design Categorizes issue or PR as related to design. labels Jun 3, 2019
@neolit123 neolit123 added this to the v1.16 milestone Jun 3, 2019
@neolit123 neolit123 mentioned this issue Jun 3, 2019
Closed
@fabriziopandini
Copy link
Member

fabriziopandini commented Jun 6, 2019 •
edited
Loading

/lifecycle active
Starting from upgrading kind in kinder + enabling multi CRI in kinder

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Jun 6, 2019
@neolit123
Copy link
Member Author

@fabriziopandini BTW, currently the kubeadm-kind jobs are pinned to kind 0.2.0 which uses docker, due to HA problems. the bump to e.g. 0.4.0 might happen post 1.16.

@fabriziopandini
Copy link
Member

@neolit123 agree; the change in kinder will be invasive, so I'm 💯 ok with waiting post release

@fabriziopandini
Copy link
Member

This was implemented with #1660
/close

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: Closing this issue.

In response to this:

This was implemented with #1660
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neolit123 neolit123

@fabriziopandini fabriziopandini

Labels
area/test kind/design Categorizes issue or PR as related to design. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
v1.16
Development

No branches or pull requests
3 participants
@neolit123 @fabriziopandini @k8s-ci-robot