Open spiffxp opened 5 years ago
:yikes:
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.
/sig testing /priority important-longterm
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
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
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: Closing this issue.
/reopen /remove-lifecycle rotten /help-wanted
@spiffxp: Reopened this issue.
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
/remove-lifecycle stale /help
@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.
@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?
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
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
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: Closing this issue.
/remove-lifecycle rotten /reopen Maybe this quarter? Or super open to any help anyone else wants to provide?
@spiffxp: Reopened this issue.
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.
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.
@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
This doc is now also missing concepts such as:
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
/remove-lifecycle stale /lifecycle frozen /milestone v1.21
/assign @BobyMCbobs
Was presented at k8s-infra meeting today. Thank you for picking this up
Good followup: depict the clusters, projects and orgs involved. Service cluster, build clusters, Google.com, kubernetes.io, etc
Kubernetes Test Infrastructure (Last updated 2020-03-04)
https://raw.githubusercontent.com/kubernetes/test-infra/master/docs/architecture.svg
2020 -> 2021 😄
this was updated pretty recently, should the follow-up be a follow-up or should we keep tracking here? if the latter we should update the milestone
Velodrome is still in the SVG.
/milestone v1.23 What I discussed during the most recent meeting is:
I'll try to clarify 1 since that's a little too vague to be actionable right now
I've taken an alternate crack at this over in https://github.com/kubernetes/k8s.io/pull/2635
It doesn't get a much into the mechanics of Prow, but more all of the other things that prow interacts with
/assign I'm not removing help as I could still use plenty of help in suggesting edits and better tools to use to document this stuff
I browsed through https://xosh.org/text-to-diagram/ to see if I could find a non-proprietary tool that could accomplish the same sort of thing I did with https://github.com/kubernetes/k8s.io/pull/2635
cc @hh
@spiffxp have we considered https://github.com/mingrammer/diagrams? Looks great.
GCP released a new diagramming tool : https://cloud.google.com/blog/topics/developers-practitioners/introducing-google-cloud-architecture-diagramming-tool
This is heavily bundled with GCP. What of AWS workloads?
This is heavily bundled with GCP. What of AWS workloads?
test-infra runs on GCP (due to https://www.cncf.io/announcements/2020/12/17/cloud-native-computing-foundation-receives-renewed-3-million-cloud-credit-grant-from-google-cloud/), FWIW.
When it isn't reasonable to DIY infra all the way down, we use off the shelf offerings sometimes. Sometimes not often enough 🙃
spiffxp is out for a while right now, I think mostly it would be good to have a rendered result like we have now.
if this is still relevant, would like to be a part /assign
At least for the Prow components, there is an architecture diagram at https://docs.prow.k8s.io/docs/overview/architecture/.
/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:
I count this as a bug since this diagram is one of the first links in our repo, and it's definitely misleading.