Aleksei Sviridkin cc731e3105 test(e2e): keep redis-tls failures legible under the op ceiling ...

The CA-projection step caps each kubectl at 30s, but more capped reads
run than its 5m op can cover, so a degraded apiserver could spend the
ceiling and leave nothing but "signal: killed". The reads now share a
step budget held under the op, and a read that hits its bound or finds
the budget spent says which read it was.

Two exec checks reported the 15s redis-cli cap for any failure, sending
a reader after a slow redis when the exec was refused or the container
was missing. They now report the exit status and what the exec
printed. The step also runs under bash with pipefail: under dash a
failed Secret read took base64's zero status and surfaced as a wrong
source name. The private-key check reads the projection already
fetched, since a second read that failed made it pass.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-03 01:42:53 +03:00

..

chainsaw-test.yaml

test(e2e): keep redis-tls failures legible under the op ceiling

2026-10-03 01:42:53 +03:00

redis-flip-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis-flip.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis.yaml

test(e2e): migrate app suite from BATS to Chainsaw and wire into CI

2026-06-25 13:42:34 +05:00