-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
Instead of synthesised "operator conditions" test we should use real create / schedule pods via deployment controller to test kube-apiserver / kcm / scheduler functionality
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-49338 cluster-kube-apiserver-operator should use pod scheduling/rollout tests for auto-regenerate-after-offline-expiry annotation
-
- Closed
-
- is blocked by
-
OCPBUGS-55217 Optimistically update Kube Server and Client CA bundles
-
- Verified
-
- is cloned by
-
OCPBUGS-49338 cluster-kube-apiserver-operator should use pod scheduling/rollout tests for auto-regenerate-after-offline-expiry annotation
-
- Closed
-
- links to
(4 links to)