You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(csv): detect deployment and requirement changes in Succeeded and Failed phases
test(csv): add unit tests for non-terminal success/failure states
feat(csv): update e2e tests with succeeded/failure transitions
refactor(sync): use generic meta object sync handler
docs(arch): update CSV FSM diagram
feat(csv): add check for conflicting APIService owners
| None | initial phase, once seen by the Operator, it is immediately transitioned to `Pending`|
73
+
| Pending | requirements in the CSV are not met, once they are this phase transitions to `Installing`|
74
+
| InstallReady | all requirements in the CSV are present, the Operator will begin executing the install strategy |
75
+
| Installing | the install strategy is being executed and resources are being created, but not all components are reporting as ready |
76
+
| Succeeded | the execution of the Install Strategy was successful; if requirements disappear, or an APIService cert needs to be rotated this may transition back to `Pending`; if an installed component dissapears this may transition to `Failed`|
77
+
| Failed | upon failed execution of the Install Strategy, or an installed component dissapears the CSV transitions to this phase; if the component can be recreated by OLM, this may transition to `Pending`|
78
+
| Replacing | a newer CSV that replaces this one has been discovered in the cluster. This status means the CSV is marked for GC|
79
+
| Deleting | the GC loop has determined this CSV is safe to delete from the cluster. It will disappear soon.|
0 commit comments