page7
8
Gaps – What E2E Does Not Cover
ZTWIM Coverege
● API / validation
No E2E checks that the validating webhook rejects invalid CRs (e.g. invalid JWT issuer, invalid TTLs, invalid resources).
● Lifecycle
Uninstall: removing CRs/operator and checking cleanup of workloads and CRDs.
Upgrade/downgrade: OLM upgrade/downgrade and operand behavior.
● Runtime and advanced config
No tests that SVIDs are issued or that the OIDC discovery endpoint works.
No explicit E2E for Route creation/availability.
External datastore, custom CA, federation .
● Security and scale
No E2E asserting SCC/RBAC behavior (partially covered by unit tests).
No load or multi-replica/scale scenarios.