actions/fluxcd-flux2
3
0
Fork 0
mirror of https://github.com/fluxcd/flux2.git synced 2026-02-08 00:37:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Added user story about verifying suspension.

Browse source 
Signed-off-by: Travis Mattera <travis@mattera.io>
This commit is contained in:
Travis Mattera 2023-11-28 19:10:43 -08:00
parent 5240376d17
commit bcbee2da4d
No known key found for this signature in database
GPG key ID: DD12726C40FD5AFD
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
rfcs/0006-alternative-suspend-control/README.md
View file

@ -91,6 +91,28 @@ as it needs to be communicated among group stakeholders.
Flux users should have a way to succinctly signal to other users why a resource
is suspended on the resource itself.
#### Suspend without Cluster Access
How do these users ensure the application is suspended?
* A validated spec field `.spec.suspend` is typesafe and can be trusted to to
suspend a resource from reconciliation.
* Logs and metrics can reveal the suspend status for confirmation. Logs are
not ideal for this use case. Metrics may be the only safe way to
confirm an object is suspended without cluster access.
What other options are there?
* The existence of the `reconcile.fluxcd.io/suspended` metadata annotation is
not typesafe and not a trustworthy way to suspend. It becomes more valid
when reported by the cli, by a controller metric/log/event, or by object
status.
* The emission of an event from a controller upon suspend or resume transition.
* The update of the object status with indication of suspended status.
### Alternatives
#### More `.spec`