add initial pass at infra diagram #2635
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's likely incomplete in a number of places, some of which I marked with TODO. This is loosely supposed to represent all of the infrastructure we manage, and the infrastructure we have yet to migrate. This was generated from hand written source, but using a google-internal tool, so I'm not sure if I can share the source from which it was generated The connections are laid out poorly by the tool, so I wouldn't pay a ton of attention to them. Roughly speaking solid lines are the path code flows as it turns into a kubernetes/kubernetes release artifact. The dotted lines are asynchronous or polling checks. The sample use case I had in my head was the first cut of an in-development release off of a release branch, thus including some testgrid dashboard changes. One thing missing off the top of my head is things that run as Prow Jobs, so some detail are missing like: - how k8s-triage is populated - how k8s-metrics is populated - how artifact promotion happens - github automation like label_sync or peribolos My preference would be to merge and iterate with this, because this is about as far as I have time to push this for now. I'm open to feedback though, and interested most specifically in things that are missing from this diagram, including external services not directly managed by us.
k8s-ci-robot
added
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
wg/k8s-infra
approved
|
Rendered as a PNG for ease of review |
|
/kind documentation |
k8s-ci-robot
added
the
kind/documentation
|
/cc @listx FYI @kubernetes/release-engineering I didn't get around to enumerating all of the releng-related projects in this pass, I'll cc in more folks specifically the next time I've got bandwidth to dig into that |
|
/cc @ameukam |
|
This is an amazing representation of what we are doing right now. We still discovering resources that need to be migrated (e.g. #1469 (comment)). /lgtm |
k8s-ci-robot
added
the
lgtm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's likely incomplete in a number of places, some of which I marked
with TODO. This is loosely supposed to represent all of the
infrastructure we manage, and the infrastructure we have yet to migrate.
This was generated from hand written source, but using a google-internal
tool, so I'm not sure if I can share the source from which it was generated
The connections are laid out poorly by the tool, so I wouldn't pay a ton
of attention to them. Roughly speaking solid lines are the path code
flows as it turns into a kubernetes/kubernetes release artifact. The
dotted lines are asynchronous or polling checks. The sample use case I had
in my head was the first cut of an in-development release off of a release
branch, thus including some testgrid dashboard changes.
One thing missing off the top of my head is things that run as Prow Jobs,
so some detail are missing like:
My preference would be to merge and iterate with this, because this is about
as far as I have time to push this for now. I'm open to feedback though,
and interested most specifically in things that are missing from this
diagram, including external services not directly managed by us.