Commits on Nov 30, 2023

1. api: introduce forceAt and resetAt annotations …

   This introduces two new annotations:
   
   - `reconcile.fluxcd.io/resetAt`: to reset the failure counts for a
     `HelmRelease` object.
   - `reconcile.fluxcd.io/forceAt`: to allow a one-off Helm install or
     upgrade when the controller would otherwise do nothing (e.g. due to
     being out of retries, in-sync, in a failed state, etc.)
   
   Both annotations require the `reconcile.fluxcd.io/requestedAt`
   annotation to be set at the same time, with the same token value.
   
   Signed-off-by: Hidde Beydals <[email protected]>

   

   hiddeco committed Nov 30, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 7a15000
   • Browse repository at this point

   Copy the full SHA

   7a15000 View commit details

   Browse the repository at this point in the history

2. Implement forceAt and resetAt annotations …

   This makes the controller actually take the
   `reconcile.fluxcd.io/forceAt` and `reconcile.fluxcd.io/resetAt` into
   account.
   
   For `reconcile.fluxcd.io/resetAt`, this means that the failure counts on
   the `HelmRelease` object are reset when the token value of the
   annotation equals `reconcile.fluxcd.io/requestedAt`. Allowing the
   controller to start over with attempting to install or upgrade the
   release until the retries count has been reached again.
   
   For `reconcile.fluxcd.io/forceAt`, this means that a one-off Helm
   install or upgrade is allowed to take place even if the object is out of
   retries, in a failed state where it should be remediated, or in-sync.
   
   Signed-off-by: Hidde Beydals <[email protected]>

   

   hiddeco committed Nov 30, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 6b7789a
   • Browse repository at this point

   Copy the full SHA

   6b7789a View commit details

   Browse the repository at this point in the history