Define a basic SLA for the hub

[bobcatfish]

Feature request

In #82 we are creating a tool to at least notify us if the hub is down, but what is less clear is what it means when it is down and how urgent it is to fix it. For example, is it so important it be up that we want folks to be on call outside of working hours?

We discussed this a bit in the hub working group and in the productivity working group, and one interesting point is that as long as the hub isn't actually hosting Tasks/Pipelines (and it isn't - just referring ppl to git, and probably eventually to an OCI registry) then the hub going down won't actually break anyone; it just makes it harder to discover Tasks.

Proposal initial SLA: we will make sure the hub is up during build cop working hours, which will vary depending on who is build cop, and will only be Monday-Friday and not include holidays.

However, a counterpoint: if folks try to visit the hub and it is down, this might give them a negative impression of the project?

Use case

As a user of Tekton, I try to visit the hub on the weekend, and find that it is down. Is it acceptable for me to wait until Monday for it to be up?

[vdemeester]

This is a requirement for being able to mark the Hub as GA (aka not hub-preview anymore).

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[bobcatfish]

Based on @vdemeester 's comment about being a GA requirement:

/lifecycle frozen