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.

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

Node testgrid dashboard cleanup #23231

Closed
3 tasks done
ehashman opened this issue Aug 12, 2021 · 27 comments · Fixed by #23333
Closed
3 tasks done

Node testgrid dashboard cleanup #23231

ehashman opened this issue Aug 12, 2021 · 27 comments · Fixed by #23333
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@ehashman
Copy link
Member

ehashman commented Aug 12, 2021

What should be cleaned up or changed:

As discussed in the SIG Node CI Subproject meeting today and last week, our testgrid dashboards are a bit of a mess:

Screenshot at 2021-08-12 12-14-04

Here is our cleanup plan:

  • Move all pr-* jobs across various tabs into a new sig-node-presubmits tab
  • Consider consolidating redundant tabs (e.g. sig-node-containerd and sig-node-containerd-io)
  • Remove double listed jobs to ensure they are filed in the right place (e.g. release-blocking jobs are already in sig-node-release-blocking and don't also need to be included under sig-node-kubelet)

Provide any links for context:

https://testgrid.k8s.io/sig-node-kubelet#node-kubelet-features-master

/cc @adisky @matthyx @ipochi
/sig node

@ehashman ehashman added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Aug 12, 2021
@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Aug 12, 2021
@matthyx
Copy link
Contributor

matthyx commented Aug 13, 2021

/assign
/assign @adisky

@matthyx
Copy link
Contributor

matthyx commented Aug 13, 2021

Here is the list of all tabs (sorted):

dashboard_groups:
- name: sig-node
  dashboard_names:
    - sig-node-cadvisor
    - sig-node-containerd
    - sig-node-containerd-io # jobs in containerd/containerd repository
    - sig-node-cos
    - sig-node-cri
    - sig-node-cri-o
    - sig-node-cri-tools
    - sig-node-critical # This dashboard contains jobs that sig-node has deemed critical to the greater operation of the sig. They should always be green.
    - sig-node-kubelet
    - sig-node-node-feature-discovery
    - sig-node-node-problem-detector
    - sig-node-ppc64le
    - sig-node-presubmits
    - sig-node-release-blocking # This is a replica of sig-node jobs that are release blocking.
    - sig-node-security-profiles-operator

Not sure which ones could be merged...

@adisky
Copy link
Contributor

adisky commented Aug 16, 2021

sig-node-critical has only one job containerd node conformance https://github.com/kubernetes/test-infra/blob/master/config/testgrids/kubernetes/sig-node/config.yaml#L22, is this critical tab needed now considering we have containerd mandatory presubmit job?

@adisky
Copy link
Contributor

adisky commented Aug 16, 2021

Also should we also think about removing windows jobs from sig-node-containerd tab?
https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-windows/windows-gce.yaml#L405

@matthyx
Copy link
Contributor

matthyx commented Aug 16, 2021

Agree with both... @ehashman wdyt?

@matthyx
Copy link
Contributor

matthyx commented Aug 18, 2021

/cc @SergeyKanzhelev

@SergeyKanzhelev
Copy link
Member

the idea of critical tab was a stepping stone to promote to release blocking as far as I remember. It didin't work as was intended

I'd vote for removing windows from containerd. But let's ping @marosset on the PR

@adisky
Copy link
Contributor

adisky commented Aug 18, 2021

the idea of critical tab was a stepping stone to promote to release blocking as far as I remember. It didin't work as was intended

Thanks for letting us know about this!! for now lets keep it as it is.

I'd vote for removing windows from containerd. But let's ping @marosset on the PR

for windows, lets wait for @marosset feedback

@marosset
Copy link
Contributor

marosset commented Aug 18, 2021

I'm OK with removing the windows tabs from sig-node-containerd.
We have Windows + containerd tests running as part of the SIG-Windows release informing dashboard https://testgrid.k8s.io/sig-windows-signal.

Since these are GCE jobs I'd like either @pjh or @ibabou to ACK this too

@ibabou
Copy link
Contributor

ibabou commented Aug 18, 2021

I'm okay with removing the windows tabs from there. ACK. Having those as part of sig-windows-gce & sig-windows-*-release is sufficient.

@pjh
Copy link
Contributor

pjh commented Aug 20, 2021

+1, removing those Windows jobs from sig-node-containerd SGTM.

@adisky
Copy link
Contributor

adisky commented Aug 20, 2021

Thanks for the inputs from windows team, Now we have two items that need PR

you can use this https://cs.k8s.io/?q=node-kubelet-master&i=nope&files=&excludeFiles=&repos=kubernetes/test-infra to search for jobs and dashboard.

@Debanitrkl
Copy link
Member

I can work on with the PR regarding removing windows jobs from containerd dasboard

@rayandas
Copy link
Member

Hey @adisky I can work on the second item (move double listed jobs to ensure they are filed in the right place).

@adisky
Copy link
Contributor

adisky commented Aug 20, 2021

@Debanitrkl @rayandas Thanks for taking this up
/assign @Debanitrkl @rayandas for the two items mentioned above

@Debanitrkl
Copy link
Member

/assign

@rayandas
Copy link
Member

/assign

@matthyx
Copy link
Contributor

matthyx commented Aug 25, 2021

Not sure we're done yet...
/reopen

@k8s-ci-robot
Copy link
Contributor

@matthyx: Reopened this issue.

In response to this:

Not sure we're done yet...
/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Aug 25, 2021
@Rajalakshmi-Girish
Copy link
Contributor

Can someone please suggest the right place to have the unit-tests tab which is currently under sig-node-ppc64le? https://k8s-testgrid.appspot.com/sig-node-ppc64le#unit-tests

This test grid seems essential to track k8s unit test failures on ppc64le.
cc @ehashman @SergeyKanzhelev @matthyx

@Rajalakshmi-Girish
Copy link
Contributor

Can someone please suggest the right place to have the unit-tests tab which is currently under sig-node-ppc64le? https://k8s-testgrid.appspot.com/sig-node-ppc64le#unit-tests

This test grid seems essential to track k8s unit test failures on ppc64le. cc @ehashman @SergeyKanzhelev @matthyx

@spiffxp @mkumatag

@mkumatag
Copy link
Member

Can someone please suggest the right place to have the unit-tests tab which is currently under sig-node-ppc64le? https://k8s-testgrid.appspot.com/sig-node-ppc64le#unit-tests
This test grid seems essential to track k8s unit test failures on ppc64le. cc @ehashman @SergeyKanzhelev @matthyx

@spiffxp @mkumatag

not sure either, wondering if we can add to some of the periodic jobs run(don't really know where are they??), worst case - lets create a new group called ibm like other groups we have in the testgrid.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 21, 2022
@ehashman
Copy link
Member Author

ehashman commented Mar 3, 2022

I have a couple more small PRs and then I think this is done.

#25497 #25496

@ehashman
Copy link
Member Author

ehashman commented Mar 3, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 3, 2022
@matthyx
Copy link
Contributor

matthyx commented Jun 1, 2022

both remaining PRs are merged
/close

@k8s-ci-robot
Copy link
Contributor

@matthyx: Closing this issue.

In response to this:

both remaining PRs are merged
/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
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.