Skip to content

Commit 885481a

Browse files
sanchezlsimonpasquier
authored andcommitted
reconcile clusteroperator status more frequently (#3006)
If status is modified, the operator must set status to proper values. This ensures that accidents cannot permanently reset status and gives a clear indication that the operator is "live". This came up as important when operators were NOT live, during cert rotations and we had no indication of problems. Signed-off-by: Luis Sanchez <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 0dbf79d283438b09c40a08429e9c8028a1a0dfbc
1 parent 6d39cbf commit 885481a

File tree

2 files changed

+2
-2
lines changed
  • staging/operator-lifecycle-manager/pkg/lib/operatorstatus
  • vendor/github.com/operator-framework/operator-lifecycle-manager/pkg/lib/operatorstatus

2 files changed

+2
-2
lines changed

staging/operator-lifecycle-manager/pkg/lib/operatorstatus/status.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ func MonitorClusterStatus(name string, syncCh <-chan error, stopCh <-chan struct
228228
// if we've reported success, we can sleep longer, otherwise we want to keep watching for
229229
// successful
230230
if successfulSyncs > 0 {
231-
time.Sleep(5 * time.Minute)
231+
time.Sleep(25 * time.Second)
232232
}
233233

234234
}, 5*time.Second, stopCh)

vendor/github.com/operator-framework/operator-lifecycle-manager/pkg/lib/operatorstatus/status.go

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)