cockroachdb / cockroachdb/cockroach-operator
Operator status should be focused on cluster health
Offen
- Vorherrschende Sprache
- Go
- Sterne
- 318
- Forks
- 104
- Ø Merge
- 1 T. 6 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
If the Cluster Status does not represent the actual state of the current cluster then I can see how it is confusing. Ideally the status is Ready, Restarting, Initializing etc to let people know if the cluster is ok or doing a specific workflow like certificate renewl or something. IMO the workflows are probably better tracked by having the operator emit events for "upgrade" or "cert renewal" or "decommissioning" etc and let the status be a quick check if the cluster is doing an operation or in stable state.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.