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

Replace kubernetes-anywhere tests with kinder tests #1543

Closed
13 tasks
fabriziopandini opened this issue Apr 27, 2019 · 9 comments
Closed
13 tasks

Replace kubernetes-anywhere tests with kinder tests #1543

fabriziopandini opened this issue Apr 27, 2019 · 9 comments
Assignees
@neolit123 @fabriziopandini
Labels
area/test lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.15

Comments

@fabriziopandini
Copy link
Member

Kinder test is there, so finally it is possible to get rid of tests using kubernetes-anywhere (which is not maintained anymore)

Currently there are following tests using kubernetes-anywhere:

  • ci-kubernetes-e2e-kubeadm-gce-1-11
  • ci-kubernetes-e2e-kubeadm-gce-1-12
  • ci-kubernetes-e2e-kubeadm-gce-1-13
  • ci-kubernetes-e2e-kubeadm-gce-1-14
  • ci-kubernetes-e2e-kubeadm-gce-master
  • ci-kubernetes-e2e-kubeadm-gce-upgrade-1-11-1-12
  • ci-kubernetes-e2e-kubeadm-gce-upgrade-1-12-1-13
  • ci-kubernetes-e2e-kubeadm-gce-upgrade-1-13-1-14
  • ci-kubernetes-e2e-kubeadm-gce-upgrade-stable-master
  • ci-kubernetes-e2e-kubeadm-gce-1-11-on-1-12
  • ci-kubernetes-e2e-kubeadm-gce-1-12-on-1-13
  • ci-kubernetes-e2e-kubeadm-gce-1-13-on-1-14
  • ci-kubernetes-e2e-kubeadm-gce-stable-on-master

The action plan is to implement a test replacement with kinder first, run both tests in parallel for some time, and then dismiss kubernetes-anywhere test as soon as we consider stable/reliable the new one

/priority important-soon
/area kubeadm
/area testing
/milestone v1.15
/assign
/lifecycle active
@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 Apr 27, 2019
@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/test labels Apr 27, 2019
@fabriziopandini fabriziopandini added this to the v1.15 milestone Apr 27, 2019
@neolit123
Copy link
Member

/assign

This was referenced Apr 29, 2019
Merged
Merged
@timothysc timothysc mentioned this issue May 3, 2019
Closed
4 tasks
@fabriziopandini
Copy link
Member Author

@neolit123 on slack
re: kubernetes-anywhere jobs. while we are soon to have replacements for everything, we can't remove all of them yet. only the upgrade ones.
the rest are present in the release-informing dashboard, so this requires sig-release/sig-testing discussion.

@fabriziopandini
Copy link
Member Author

Current status about release informing is:

  • gce-master is in sig-release-master-informing
  • gce-1-14 is in sig-release-1.14-all
  • gce-1-13 is in sig-release-1.13-all
  • gce-1-12 is in sig-release-1.12-all
  • gce-1-11 is missing from sig-release-1.11-all, this seems an error
  • gce-upgrade-stable-master is in sig-release-master-informing
  • gce-upgrade-1-13-1-14 is in sig-release-1.14-all
  • gce-upgrade-1-12-1-13 is in sig-release-1.13-all
  • gce-upgrade-1-11-1-12 is in sig-release-1.12-all
  • gce-stable-on-master is in sig-release-master-informing
  • gce-1-13-on-1-14 is in sig-release-1.14-all
  • gce-1-12-on-1-13 is in sig-release-1.13-all
  • gce-1-11-on-1-12 is missing from sig-release-1.12-all, this seems an error

@fabriziopandini
Copy link
Member Author

fabriziopandini commented May 5, 2019 •
edited
Loading

About run frequency:

  • gce jobs every 2h for master, every 12h for an older releases
  • gce-upgrade jobs every 6h for master, every 12h for an older releases
  • gce-x-on-y jobs every 4h for master, every 12h for an older releases
  • [kind jobs every 1h for master, every 4h for an older releases]

@fabriziopandini
Copy link
Member Author

fabriziopandini commented May 5, 2019 •
edited
Loading

About notifications:

  • gce jobs (with the exception of 1.11) send notifications after failing for 24h
  • gce-upgrade jobs do not send notification
  • gce-x-on-y jobs, only for stable-on-master, send notifications after failing for 24h
  • [kind jobs send notifications after failing for 24h]

@fabriziopandini
Copy link
Member Author

fabriziopandini commented May 5, 2019 •
edited
Loading

wrap up: the proposal to be discussed next kubeadm office hours is:

  • gce jobs are going to be deleted in favor of kubeadm-kind* jobs
  • gce-upgrade jobs are going to be deleted in favor of kubeadm-kinder-upgrade* jobs
  • gce-x-on-y jobs are going to be deleted in favor of kubeadm-kinder-x-on-y* jobs
  • sig release dashboard will be updated accordingly, and misconfiguration fixed
  • run frequency will be harmonized on every 2h for master, every 12h for an older releases
  • notification will be harmonized and everything will send notifications after failing for 24h
  • to create a new sig-cluster-lifecycle-kubeadm dashboard

cc @neolit123 @rosti @timothysc

@neolit123
Copy link
Member

i think i went ahead of the office hours meeting and i've sent this PR that already merged:
kubernetes/test-infra#12493

kubeadm-gce* is no longer present in release -informing and -all dashboards.
kinder jobs are now in place of skew and upgrade jobs.

the remaining tasks here are:

  • remove kubeadm-gce* from both job definitions and testgrid dashboards.
  • restructure our SIG dashboards as see fit.

@fabriziopandini fabriziopandini mentioned this issue May 11, 2019
Merged
@fabriziopandini
Copy link
Member Author

After merging
kubernetes/test-infra#12591
kubernetes/test-infra#12592

/close

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: Closing this issue.

In response to this:

After merging
kubernetes/test-infra#12591
kubernetes/test-infra#12592

/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 lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.15
Development

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