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
At present the controllers mark a resource with a Ready==False state when a user defines the resource as suspended using .spec.suspend.
Given the aim of this value is to pause all reconciliation actions, this behavior is not accurate to the goal of the field. We must simply stop reconciling and observing state, and leave any previous observed state untouched as a "freeze in time".
To still make the state visible to the user, we must add an addition printer column that shows the .spec.suspend state of the resource (example here: fluxcd/helm-controller#162), and a column to the flux get [source] commands.
helm-controller
source-controller
kustomize-controler
add "suspended" column to flux get [source] commands
The text was updated successfully, but these errors were encountered:
At present the controllers mark a resource with a
Ready==False
state when a user defines the resource as suspended using.spec.suspend
.Given the aim of this value is to pause all reconciliation actions, this behavior is not accurate to the goal of the field. We must simply stop reconciling and observing state, and leave any previous observed state untouched as a "freeze in time".
To still make the state visible to the user, we must add an addition printer column that shows the
.spec.suspend
state of the resource (example here: fluxcd/helm-controller#162), and a column to theflux get [source]
commands.flux get [source]
commandsThe text was updated successfully, but these errors were encountered: