Test-infra: The test-infra architecture diagram is out of date
/kind documentation
/kind bug
I visited https://github.com/spiffxp/test-infra/blob/write-some-docs/docs/architecture.svg and saw an architecture that is wildly out of date, eg:
- has mungegithub
- has tot
- missing boskos
- missing spyglass
I count this as a bug since this diagram is one of the first links in our repo, and it's definitely misleading.
spiffxp
All 23 comments
:yikes:
stevekuznetsov
on 18 Jun 2019
While this bug is still open, I recommend checking out the SIG Testing Intro presented a KubeCon NA 2018, find video and slides at https://github.com/kubernetes/community/tree/master/sig-testing#presentations. The final diagram is a bit dense so I tried to walk through how we got to the rube goldberg thing we have going on now.
spiffxp
on 25 Jun 2019
/sig testing
/priority important-longterm
spiffxp
on 1 Aug 2019
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
on 30 Oct 2019
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
fejta-bot
on 29 Nov 2019
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 30 Dec 2019
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.
k8s-ci-robot
on 30 Dec 2019
/reopen
/remove-lifecycle rotten
/help-wanted
spiffxp
on 1 Jan 2020
@spiffxp: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
/help-wanted
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
on 1 Jan 2020
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
on 31 Mar 2020
/remove-lifecycle stale
/help
spiffxp
on 1 Apr 2020
@spiffxp:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/remove-lifecycle stale
/help
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
on 1 Apr 2020
@spiffxp I'd like to help out here both in creating a new diagram and documenting other parts of the repo. For instance, I was recently looking at the kubekins-e2e image because it is so prevalent across jobs and there is pretty minimal documentation on it and other Docker images used. I wonder what would be a good format for a sort of "Intro to test-infra" guide. This may be outside the scope of this issue, but I wanted to see if you had thoughts on the matter?
hasheddan
on 4 Apr 2020
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
on 3 Jul 2020
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
fejta-bot
on 2 Aug 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 1 Sep 2020
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.
k8s-ci-robot
on 1 Sep 2020
/remove-lifecycle rotten
/reopen
Maybe this quarter? Or super open to any help anyone else wants to provide?
spiffxp
on 10 Sep 2020
@spiffxp: Reopened this issue.
In response to this:
/remove-lifecycle rotten
/reopen
Maybe this quarter? Or super open to any help anyone else wants to provide?
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
on 10 Sep 2020
Hi @spiffxp Do you have a source file for SVG file or drawing tool preference?
I quickly mocked up a replica of the out-of-date SVG using dia which I would be happy to share with you.
RobertKielty
on 14 Sep 2020
Nothing helpful to comment on but simply adding that I would love to see this as someone who would like to learn how it all works.
leeyspaul
on 15 Oct 2020
@RobertKielty No drawing tool preferences as long as it can be updated by community members
https://docs.google.com/presentation/d/1HOQ2df_AT-vIuz-JNaJol2oiGq84m50h9T49_5WgEaI/edit#slide=id.g4a3c5dc660_0_539 are the slides I walked through back in dec 2018
spiffxp
on 29 Oct 2020
This doc is now also missing concepts such as:
- whether the infrastructure runs in the google.com GCP org or in the kubernetes.io GCP org
- prow build clusters vs. service clusters
- velodrome no longer exists
- the use of GCB / GCR by image-pushing jobs
spiffxp
on 29 Oct 2020
Related issues
spzala
路
4Comments
BenTheElder
路
4Comments
cjwagner
路
3Comments
BenTheElder
路
4Comments
MrHohn
路
4Comments
Most helpful comment
@spiffxp I'd like to help out here both in creating a new diagram and documenting other parts of the repo. For instance, I was recently looking at the
kubekins-e2eimage because it is so prevalent across jobs and there is pretty minimal documentation on it and other Docker images used. I wonder what would be a good format for a sort of "Intro to test-infra" guide. This may be outside the scope of this issue, but I wanted to see if you had thoughts on the matter?