LinuxCommandLibrary
GitHubF-DroidGoogle Play Store

flux-resume

Resume reconciliation of suspended Flux resources

TLDR

Resume a Kustomization
$ flux resume kustomization podinfo
copy
Resume several Kustomizations
$ flux resume kustomization podinfo-1 podinfo-2
copy
Resume every Kustomization in the namespace
$ flux resume kustomization --all
copy
Resume a HelmRelease
$ flux resume helmrelease podinfo
copy
Resume a GitRepository source
$ flux resume source git my-repo
copy
Resume an ImageUpdateAutomation
$ flux resume image update my-automation
copy

SYNOPSIS

flux resume kind [name ...] [options]

DESCRIPTION

flux resume clears suspension on a Flux custom resource so its controller reconciles it again. The command waits for that reconciliation to finish.The resource name is required unless --all is set, which resumes every matching object in the namespace (default `flux-system`). Multiple names may be given in one invocation. --wait resumes them one at a time, waiting for each to reconcile before the next.Short kind aliases such as `ks` for kustomization and `hr` for helmrelease are accepted.

PARAMETERS

--all

Resume all resources of the given kind in the namespace.
--wait
Wait for one resource to reconcile before moving to the next.
-n, --namespace ns
Namespace scope for the CLI request (default `flux-system`).
--timeout duration
Timeout for the operation (default `5m0s`).
--kubeconfig file
Path to the kubeconfig file.
--context name
Kubeconfig context to use.

KINDS

kustomization

Resume a Kustomization.
helmrelease
Resume a HelmRelease.
source git, source helm, source oci, source bucket, source chart
Resume a GitRepository, HelmRepository, OCIRepository, Bucket, or HelmChart.
image policy, image repository, image update
Resume ImagePolicy, ImageRepository, or ImageUpdateAutomation objects.
alert, alert-provider, receiver
Resume notification Alerts, Providers, and Receivers.

INSTALL

sudo apk add flux
copy
brew install flux
copy
nix profile install nixpkgs#flux
copy

CAVEATS

Resume clears `spec.suspend` on the live object and then waits for a reconcile. A Git source that still sets suspension will suspend the object again on the next sync. Cluster access via kubectl is required.

SEE ALSO

RESOURCES

Copied to clipboard
Kai