|
2 | 2 |
|
3 | 3 | ## Summary |
4 | 4 |
|
5 | | -Ironic Standalone Operator should emit Kubernetes Events on the `Ironic` custom resource to make |
6 | | -reconciliation progress and failures visible to cluster users (`kubectl describe |
7 | | -ironic ...`), without flooding the cluster with repetitive messages. |
| 5 | +Ironic Standalone Operator should emit Kubernetes Events on the `Ironic` |
| 6 | +custom resource to make reconciliation progress and failures visible to |
| 7 | +cluster users (`kubectl describe ironic ...`), without flooding the cluster |
| 8 | +with repetitive messages. |
8 | 9 |
|
9 | 10 | This document proposes a small, stable set of **Event reasons**, their **types** |
10 | 11 | (Normal/Warning), and the **conditions under which they are recorded**. |
@@ -93,11 +94,11 @@ need explicit breadcrumbs. |
93 | 94 | ## Testing plan |
94 | 95 |
|
95 | 96 | - Add unit tests for event emission in the controller using a fake recorder: |
96 | | - - Ready transition emits `IronicReady` once. |
97 | | - - Missing Secret/ConfigMap emits `SecretNotFound` / `ConfigMapNotFound`. |
98 | | - - Transient reconcile errors emit `ReconcileFailed`. |
| 97 | + - Ready transition emits `IronicReady` once. |
| 98 | + - Missing Secret/ConfigMap emits `SecretNotFound` / `ConfigMapNotFound`. |
| 99 | + - Transient reconcile errors emit `ReconcileFailed`. |
99 | 100 | - Validate via e2e/functional tests (optional, if already covering these flows): |
100 | | - - Deploy an `Ironic` CR and assert at least one `IronicReady` event appears. |
| 101 | + - Deploy an `Ironic` CR and assert at least one `IronicReady` event appears. |
101 | 102 |
|
102 | 103 | ## Compatibility and upgrade considerations |
103 | 104 |
|
|
0 commit comments