Assign and enforce SIG ownership of all kubernetes/kubernetes e2e tests

[Aaron Crickenberger]

Hi all,

I think it's relevant to WG Reliability's mission that we ensure all kubernetes/kubernetes e2e tests have SIG ownership defined by a [sig-foo] tag in the test's name.  As of the time I created a tracking issue for this [1], there were 96 untagged e2e tests.

SIG Testing can implement enforcement of this policy, but we would like your help in deciding who should own these tests.  I've cc'ed sig-arch because I think it's the relevant SIG to make these assignments, and because some of these tests are tagged as Conformance.

The v1.21 test freeze is currently listed as March 24th [2], is it fair to expect completion of this before then?

- aaron

[1]: https://github.com/kubernetes/kubernetes/issues/98326

[2]: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.21#tldr

[Davanum Srinivas]

Aaron,

I think March 24th is fair to do this. Also cc-ing sig-node as there's 60 of them that are marked "[NodeConformance]"

Sergey, Elana,

Can you please tag the sig-node related tests first? (60 out of the 96 automatically fall under sig-node, am sure there are a few more just from a rapid scan)

Aaron,

Whatever remains, we can go through it in an upcoming sig-arch meeting and assign it to different sigs.

thanks,

Dims

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CALOex7vPr0HnTJwYOmEby2sdVmLbPMei3Tv%2Bg5QfKKLNh%2B8iBw%40mail.gmail.com.

--

Davanum Srinivas :: https://twitter.com/dims

[Wojciech Tyczyński]

On Wed, Feb 10, 2021 at 8:01 AM Davanum Srinivas <dav...@gmail.com> wrote:

Aaron,

I think March 24th is fair to do this. Also cc-ing sig-node as there's 60 of them that are marked "[NodeConformance]"

Sergey, Elana,

Can you please tag the sig-node related tests first? (60 out of the 96 automatically fall under sig-node, am sure there are a few more just from a rapid scan)

Aaron,

Whatever remains, we can go through it in an upcoming sig-arch meeting and assign it to different sigs.

+1

I've just sent a PR to tag few autoscaling tests. I agree that we should first attack NodeConformance once to signiifcantly reduce the size of this list

and  then it will be easier to track them.

thanks,

Dims

On Tue, Feb 9, 2021 at 6:09 PM Aaron Crickenberger <spi...@gmail.com> wrote:

Hi all,

I think it's relevant to WG Reliability's mission that we ensure all kubernetes/kubernetes e2e tests have SIG ownership defined by a [sig-foo] tag in the test's name.  As of the time I created a tracking issue for this [1], there were 96 untagged e2e tests.

SIG Testing can implement enforcement of this policy, but we would like your help in deciding who should own these tests. 

Yeah - I think it's important to think how we can not regress in the future here. Do I understand correctly that you're volunteering SIG testing to do that?

 

I've cc'ed sig-arch because I think it's the relevant SIG to make these assignments, and because some of these tests are tagged as Conformance.

The v1.21 test freeze is currently listed as March 24th [2], is it fair to expect completion of this before then?

- aaron

[1]: https://github.com/kubernetes/kubernetes/issues/98326

[2]: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.21#tldr

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-architecture" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-arch...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-architecture/CALOex7vPr0HnTJwYOmEby2sdVmLbPMei3Tv%2Bg5QfKKLNh%2B8iBw%40mail.gmail.com.

--

Davanum Srinivas :: https://twitter.com/dims

--

You received this message because you are subscribed to the Google Groups "kubernetes-wg-reliability" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-wg-reli...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-wg-reliability/CANw6fcGfUsiDWmsRc8bC_HKJt0V4P6HUWQkpCvO%3Ds%2B%2B1%2BBdvhA%40mail.gmail.com.