Decide semantics of predicate precomputations.

[jayunit100]

Problem

Some predicates may need precomputations or "preconditions" to be met before they can run.

• As of now, those preconditions may or may not be gauranteed to exist in the predicateMetadata struct.
• Some of those predicates may be able to bootstrap some of their own data (by redoing a query, if the predicate metadata is incomplete).

Solution

We should decide wether (1) predicates should try to create data which is precomputed and (2) if so, what the best way to do this is which is scalable and doesnt lead to duplication of error handling/querying.

Two possible solutions:

• make any predicate's precompute function (as of now, really we only have one - but there may be others) stand alone - so that it can be called outside of the standard precomputation steps provided by the scheduler framework (this might help in corner cases - i.e. if a query fails randomly, the predicate has a retry built-in - but it will lead to duplication of logic).
• Each predicates precompute function stays encapsulated, and predicates simply have preconditions of checking for missing data (this is simpler to maintain from the code perspective, but might be some corner cases where it hurts us). Once we decide, we would update the predicates_test functions where necessary to include test cases for when precomputation is enabled.

@wojtek-t Suggesting this as a follow on to #33763 .

[jayunit100]

As of now, i think we leaned towards

• putting the precomputations as attachments to the predicates,
• re-running precomputations inside the predicate evaluation if there is missing info

1. is that the standard for all predicates
2. can that be abstracted into a predicate interface of some sort?

[wojtek-t]

Re 1) - yes, I believe this is what we are doing for all predicates now.

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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
/remove-lifecycle stale

[fejta-bot]

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