Skip to content

Commit 001e75c

Browse files
committed
fix lint errors
Signed-off-by: Vishal Anarase <iamvishalanarase@gmail.com>
1 parent a67ad96 commit 001e75c

1 file changed

Lines changed: 8 additions & 7 deletions

File tree

design/ironic-standalone-operator/reconciliation-events.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22

33
## Summary
44

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.
89

910
This document proposes a small, stable set of **Event reasons**, their **types**
1011
(Normal/Warning), and the **conditions under which they are recorded**.
@@ -93,11 +94,11 @@ need explicit breadcrumbs.
9394
## Testing plan
9495

9596
- 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`.
99100
- 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.
101102

102103
## Compatibility and upgrade considerations
103104

0 commit comments

Comments
 (0)