flux-operations
Skill19 starsChanged 10 months agoMITView on GitHub
Use when forcing immediate reconciliation, suspending reconciliation for maintenance, rolling back failed deployments, upgrading Flux components, managing drift detection, or performing multi-cluster Flux operations
- Commits and pushes
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cert-manager-troubleshootingSkill
- external-dns-troubleshootingSkill
- external-secrets-troubleshootingSkill
- flux-gitops-patternsSkill
- flux-troubleshootingSkill
- helm-chart-developmentSkill
- helm-chart-maintenanceSkill
- helm-chart-reviewSkill
- helm-chart-testingSkill
- k8s-continual-improvementSkill
- k8s-dns-troubleshootingSkill
- k8s-namespace-troubleshootingSkill
- k8s-network-troubleshootingSkill
- k8s-platform-operationsSkill
- k8s-platform-tenancySkill
- k8s-security-hardeningSkill
- k8s-security-redteamSkill
- kyverno-troubleshootingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 206
Always resume suspended resources: - Don't leave resources suspended indefinitely
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flux CD Operations
Manage Flux CD reconciliation operations including suspend, resume, force sync, rollback, and multi-cluster management.
Keywords
flux, fluxcd, reconcile, suspension, resumption, sync, rollback, rolling back, drift, helmrelease, kustomization, gitops, operations, management, upgrade, upgrading, failure, failed, debugging, debug
When to Use This Skill
- Need to force immediate reconciliation
- Suspending reconciliation for maintenance
- Rolling back a failed deployment
- Upgrading Flux components
- Managing drift detection
- Multi-cluster Flux operations
Related Skills
- flux-troubleshooting - Diagnosing issues
- flux-gitops-patterns - Architecture patterns
- k8s-platform-operations - General cluster operations
Quick Reference
| Task | Command |
| Force sync all | flux reconcile ks flux-system --with-source |
| Suspend resource | flux suspend ks <name> -n <ns> |
| Resume resource | flux resume ks <name> -n <ns> |
| Check status | flux get all -A |
| View diff | flux diff ks <name> --path <local> |
Reconciliation Management
Force Immediate Reconciliation
flux reconcile kustomization <name> -n <namespace> --with-source
flux reconcile helmrelease <name> -n <namespace> --with-source
flux reconcile source git <name> -n <namespace>
flux reconcile source oci <name> -n <namespace>
flux reconcile source helm <name> -n <namespace>Suspend Reconciliation
flux suspend kustomization <name> -n <namespace>
flux suspend helmrelease <name> -n <namespace>
flux suspend source git <name> -n <namespace>GitOps method (persisted, recommended):
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: <name>
spec:
suspend: trueResume Reconciliation
flux resume kustomization <name> -n <namespace>
flux resume helmrelease <name> -n <namespace>Rollback Strategies
Git Revert (Recommended)
git log --oneline -10
git revert <commit-sha>
git push origin main
flux reconcile kustomization flux-system --with-sourceVersion Pin
spec:
chart:
spec:
version: "1.2.3"Emergency Helm Rollback
flux suspend helmrelease <name> -n <namespace>
helm history <release-name> -n <namespace>
helm rollback <release-name> <revision> -n <namespace>
flux resume helmrelease <name> -n <namespace>Drift Detection
Enable Drift Detection
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
spec:
driftDetection:
mode: enabled # or 'warn'
ignore:
- paths: ["/spec/replicas"]
target:
kind: Deployment
- paths: ["/metadata/annotations"]
target:
kind: ServiceCheck for Drift
kubectl get helmrelease <name> -n <ns> -o jsonpath='{.status.drift}'
flux diff kustomization <name> --path ./path/to/localFlux Upgrade Procedures
Check Current Version
flux version
flux checkUpgrade Flux
brew upgrade fluxcd/tap/flux
flux install --export > flux-system/gotk-components.yaml
git add -A && git commit -m "Upgrade Flux to $(flux version --client)"
git pushUpgrade with Bootstrap
flux bootstrap github \
--owner=<org> \
--repository=<repo> \
--branch=main \
--path=./clusters/production \
--personalMulti-Cluster Operations
Switch Context
kubectl config get-contexts
kubectl config use-context <cluster-name>
flux checkCross-Cluster Source Reference
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
name: shared-config
spec:
url: https://github.com/org/shared-config
ref:
branch: mainHelmRelease Configuration
Remediation Settings
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
spec:
install:
remediation:
retries: 3
upgrade:
remediation:
retries: 5
remediateLastFailure: true
cleanupOnFail: true
rollback:
timeout: 5m
recreate: false
force: false
cleanupOnFail: false
test:
enable: trueDisable Health Checks
spec:
install:
disableWait: true
upgrade:
disableWait: trueGitOps Best Practices
- Prefer Git operations - Rollbacks via git revert maintain audit trail
- Always resume suspended resources - Don't leave resources suspended indefinitely
- Use --with-source - Ensures source is refreshed during reconciliation
- Check dependsOn chains - Child resources need parents reconciled first
- Document suspensions - Note why and when in commit messages
MCP Tools Available
mcp__flux-operator-mcp__reconcile_flux_kustomizationmcp__flux-operator-mcp__reconcile_flux_helmreleasemcp__flux-operator-mcp__reconcile_flux_sourcemcp__flux-operator-mcp__suspend_flux_reconciliationmcp__flux-operator-mcp__resume_flux_reconciliation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

