Sig-release: Create some more CI signal documentation

[alejandrox1]

This issue may go with #1223 .
Overall, it would be good to have some video and writing on what the following tools are and how to use them

• [ ] Testgrid https://testgrid.k8s.io/
• [ ] Triage https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&job=pull-kubernetes-e2e-gce
• [ ] Prow
• [ ] Prow monitoring https://monitoring.prow.k8s.io/?orgId=1
• [ ] Prow status https://prow.k8s.io/
• [ ] Prow tide pool https://prow.k8s.io/tide
• [ ] GCP Prow dashboards https://github.com/kubernetes/k8s.io/blob/85a327269e221e9e4afd9846a4606327334bf1ba/groups/groups.yaml#L610
• [ ] How e2e testswork
• [ ] What the role of Ginkgo is and how we use it

/assign
/assign @hasheddan @roberthbailey
/kind documentation
/priority important-soon

[hasheddan]

/assign @RobertKielty
/unassign @roberthbailey

Just a guess ;)

[hasheddan]

I can get started by writing up an outline for testgrid :+1:

[alejandrox1]

I'll work backwards then, and take "how e2e tests work"

[RobertKielty]

I'd also be interested in reading about how to understand Kubernetes behaviour by reading an e2e test.

[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

[thejoycekung]

PR around more CI signal docs: https://github.com/kubernetes/community/pull/5449

[justaugustus]

/remove-lifecycle rotten
/area release-team
/sig release testing

[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-contributor-experience at kubernetes/community.
/lifecycle stale