Ahmet Alp Balkan 4d3f5cdc82 kubelet: Add description for failed predicate Events ...

**Problem:** When a Pod fails to run due to kubelet-side admission checks, the
v1.Event objects emitted looks like these:

    Reason="NodeAffinity" Message="Predicate NodeAffinity failed"
    Reason="NodeName" Message="Predicate NodeName failed"
    Reason="NodePorts" Message="Predicate NodePorts failed"

**Solution:** Expose human-readable predicate description in the failure
so that kubelet submits an Event with this description, such as:

    Reason="NodeAffinity" Message="Predicate NodeAffinity failed: node(s) didn't match Pod's node affinity/selector"
    Reason="NodeName" Message="Predicate NodeName failed: node(s) didn't match the requested node name"
    Reason="NodePorts" Message="Predicate NodePorts failed: node(s) didn't have free ports for the requested pod ports"

2024-06-13 15:12:56 -07:00

..

admission_failure_handler_stub.go

…

doc.go

…

handlers_test.go

Cleanup defer from SetFeatureGateDuringTest function call

2024-04-24 20:25:29 +02:00

handlers.go

…

interfaces.go

…

predicate_test.go

Get rid of unused API type NodeResources

2024-03-01 15:13:50 -08:00

predicate.go

kubelet: Add description for failed predicate Events

2024-06-13 15:12:56 -07:00