Kind: document kubetest integration

[BenTheElder]

https://github.com/kubernetes-sigs/kind/issues/161#issuecomment-460105113

We have integration now, but it's not really documented. Possibly pointers could live in the upstream developer e2e test docs as hack/local-up-cluster.sh does currently and/or some docs could live in test-infra.

We should also at least point to those docs from kind's own docs once they exist, but the full contents may not belong here.

[neolit123]

i cannot find any docs about hack/local-up-cluster.sh in k/k and k/test-infra. but if there is an exact location e.g. file/folder i guess can help.

[BenTheElder]

The main docs I know of for k/k devel are actually in k/community, in particular I think this is the canonical e2e doc: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md

[neolit123]

ok, i forgot about those.

i think we might want to start on the docs only after we have jobs using the deployer.
my work on kubeadm-kind-<branch-name> is starting next week.

[neolit123]

/assign

[neolit123]

/kind documentation

[neolit123]

might as well wait for kubetest2 TBH.

[BenTheElder]

SGTM

[BenTheElder]

we do have jobs using the deployer, maybe we should go ahead and document how to use this with kubetest, kubetest2 might be a bit... (it looks like a teammate will ramp up on this and get to it ... soonish ??)

[neolit123]

i have a TODO to document how to test the e2e framework for new contributors:
https://github.com/kubernetes/kubernetes/issues/76833
these tickets seem to overlap, although there were concern from the testing-commons group that they don't want these docs in k/community because they find the existing docs there confusing /shrug.

when i get time, i might as well send to:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md
and see how that goes.

[BenTheElder]

SGTM, if not we can put docs in the kind docs, either way we should at
least link out to those from the kind site.

Thanks :-)

On Thu, May 2, 2019 at 5:09 PM Lubomir I. Ivanov [e-mail]
wrote:

i have a TODO to document how to test the e2e framework for new
contributors:
kubernetes/kubernetes#76833
https://github.com/kubernetes/kubernetes/issues/76833
these tickets seem to overlap, although there were concern from the
testing-commons group that they don't want these docs in k/community
because they find these docs confusing /shrug.

when i get time, i might as well send to:

https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md
and see how that goes.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/262#issuecomment-488875214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHADK7CTV72N2SCVVPEY33PTN7CFANCNFSM4GUBVFIQ
.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[BenTheElder]

we have other issue tracking improving the docs, and kubetest / kubetest2 hasn't really shaken out.