Skip to content

Make link checker resilient to transient external failures#89

Open
anisurrahman75 wants to merge 1 commit into
masterfrom
fix-flaky-link-checker
Open

Make link checker resilient to transient external failures#89
anisurrahman75 wants to merge 1 commit into
masterfrom
fix-flaky-link-checker

Conversation

@anisurrahman75

Copy link
Copy Markdown
Member

Problem

Master CI intermittently failed on the Check links step with:

[ERROR] https://kubernetes.io/... | Connection failed. Check network connectivity and firewall settings

The reported URLs are actually valid (HTTP 200). The failing set rotated run-to-run and the same commits passed on re-run — classic transient flakiness. kubernetes.io was intermittently rate-limiting / refusing connections from the runner, which hit external sites at concurrency 10 with no retries.

Fix

Tune the lychee invocation:

  • --max-concurrency 10 → 4 (less aggressive, avoids rate-limit triggers)
  • --max-retries 6 — retry transient failures instead of failing the build
  • --retry-wait-time 5 — back off between retries
  • --timeout 30 — tolerate slow responses

Verified locally with lychee v0.24.2 and the new flags: 0 Errors.

The lychee link checker intermittently failed on master with
"Connection failed. Check network connectivity and firewall settings"
against kubernetes.io URLs that are actually valid (HTTP 200). The
runner was hitting external sites with no retries and high concurrency,
triggering rate-limiting / connection refusals.

Lower --max-concurrency to 4 and add --max-retries 6,
--retry-wait-time 5 and --timeout 30 so transient failures are retried
instead of failing the build.

Signed-off-by: Anisur Rahman <anisur@appscode.com>
@github-actions

Copy link
Copy Markdown

Visit the preview URL for this PR (updated for commit 7e26cc2):

https://kubestash-qa--pr89-fix-flaky-link-check-glyc3s0d.web.app

(expires Fri, 26 Jun 2026 06:31:15 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 7765752f86b485f0f549c1d5d58c61af5e2ecd74

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