Skip to content

Merge to main: Merge to soperator-release-3.0: Backport: Add retry wrapper for FluxCD kubectl provisioners#881

Merged
theyoprst merged 3 commits intomainfrom
merge-to-main-from/merge-to-soperator-release-3.0-from/SCHED-1167/flacky-fluxcd-install
Mar 18, 2026
Merged

Merge to main: Merge to soperator-release-3.0: Backport: Add retry wrapper for FluxCD kubectl provisioners#881
theyoprst merged 3 commits intomainfrom
merge-to-main-from/merge-to-soperator-release-3.0-from/SCHED-1167/flacky-fluxcd-install

Conversation

@github-actions
Copy link
Contributor

Merge back to main of the Pull Request #880 by @theyoprst

Original PR Description

Merge back to soperator-release-3.0 of the Pull Request #878 by @theyoprst

Original PR Description

Summary

Problem

E2E tests fail intermittently during terraform apply when kubectl apply installs FluxCD:

read tcp 10.1.0.159:43748->89.124.41.133:443: read: connection reset by peer

Recent failure: run #23168190466


You cannot skip this merge, but if you really don't want these changes (conflicts or doesn't make sense), just comment /revert-last-pr, and wait for the revert to come, then merge this PR (even if 0 changes).

Transient k8s API unavailability can cause the flux_namespace and flux2
local-exec provisioners to fail on first attempt. A shared retry.sh script
(5 retries, 2 s interval by default) is placed in modules/scripts/ and
referenced from both provisioners so they recover automatically.
Backport: Add retry wrapper for FluxCD kubectl provisioners
…om/SCHED-1167/flacky-fluxcd-install

Merge to soperator-release-3.0: Backport: Add retry wrapper for FluxCD kubectl provisioners
@theyoprst theyoprst merged commit 9afbd8d into main Mar 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant