Skip to content

Comments

feat(yurt-iot-dock): add --skip-preflight-checks flag to bypass prefl…#2527

Open
amuammer wants to merge 2 commits intoopenyurtio:masterfrom
amuammer:feature/yurt-iot-dock-skip-preflight-checks
Open

feat(yurt-iot-dock): add --skip-preflight-checks flag to bypass prefl…#2527
amuammer wants to merge 2 commits intoopenyurtio:masterfrom
amuammer:feature/yurt-iot-dock-skip-preflight-checks

Conversation

@amuammer
Copy link

@amuammer amuammer commented Feb 18, 2026

What type of PR is this?

/kind feature
/sig iot

What this PR does / why we need it:

Adds a new --skip-preflight-checks flag to yurt-iot-dock that allows
bypassing the preflight namespace validation check on startup.

In some edge deployment scenarios (restricted RBAC, bootstrapping, or
environments where the namespace exists but is temporarily unreachable),
the preflight check fails and causes the controller to exit immediately,
even when the rest of the system is functional.

This flag gives operators the flexibility to skip the check when needed.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

The flag defaults to false, so existing behavior is completely unchanged.
Only when --skip-preflight-checks=true is explicitly passed will the
preflight check be skipped.

Changes:

  • cmd/yurt-iot-dock/app/options/options.go: Added SkipPreflightChecks bool field and registered the flag
  • cmd/yurt-iot-dock/app/core.go: Guarded the preflight block with the new flag

Does this PR introduce a user-facing change?

Added `--skip-preflight-checks` flag to yurt-iot-dock. When set to `true`, 
the preflight namespace validation check is skipped on startup. Defaults to `false`.

Exmaple


yurt-iot-dock --nodepool=edge-pool --skip-preflight-checks=true

@amuammer amuammer requested a review from a team as a code owner February 18, 2026 01:18
@sonarqubecloud
Copy link

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