|
- gitops - Is there a way to manually retry a HelmRelease for FluxCD . . .
To force a HelmRelease reconciliation, you could use a combination of the suspend and resume commands You can also use the flux reconcile command: The reconcile kustomization command triggers a reconciliation of a HelmRelease resource and waits for it to finish
- Deployment out of Sync Helm Release stuck in Pending-Upgrade
Flux auto updates the helm release to the newest image tag (as usual) but the deployment resource gets stuck on the out dated image tag If you run fluxctl list-images you'll see the helm release pointing to the correct version, but the deployment is pointed to an outdated version
- Runbook: Fixing flux sync timeout - GitHub Wiki SEE
resource when it fails It appears that the sync timeout for us is caused by not properly deleting old ingresses or load balancer resources How to fix it Go to 503-for-pending-subscriptions under “Ingresses“ in Lens Click the pencil icon on the top right side to edit the ingress definition
- Troubleshooting – Flux
To resolve this problem, move the first line farther below in your etc hosts file, beneath the line that lists your computer’s real (routable) IP address and host name If a database deadlock occurs while your workflow is firing, the database transaction is rolled back and tried again automatically
- flux stuck and does not recover · Issue #3044 · fluxcd flux - GitHub
Describe the bug After a few days flux got stuck and did not sync anymore I killeded the pod and everything was up and running again To Reproduce I have no idea maybe the network connection was brokene for a few minutes or the file
- failed to determine sync action for release: status failed of release . . .
Well, I expect to have Flux getting sync with my latest update on the repo Logs If applicable, please provide logs of fluxd In a standard stand-alone installation of Flux, you'd get this by running kubectl logs deploy flux -n flux Additional context Flux version: 1 19 0 Kubernetes version: 1 16 Git provider: Github Container registry provider
- Adding CRDs to Flux repo leads to high sync time and CPU usage
While our git repository is fairly big, we recently added Prometheus-Operator CRDs (https: github com helm charts tree master stable prometheus-operator crds) That single change lead to a high CPU usage and Flux is now taking a long time to sync In our case, we are reaching the 5 minutes timeout
- Running fluxctl sync does not apply manifests #2818 - GitHub
When doing a manual sync, with fluxctl sync flux does not apply the current manifests Nothing gets applied until the next sync-interval time We expect flux sync to apply the manifests immediately and not wait for sync-interval to occur
|
|
|