fix: wait for cillium policy until CRDs are ready

[ogzhanolguncu]

What does this PR do?

ctlptl apply starts minikube with --wait=all, which blocks until all system pods are ready

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready	Preview, Comment	Feb 17, 2026 9:00am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
engineering	Ignored	Preview	Feb 17, 2026 9:00am

[coderabbitai]

📝 Walkthrough

Walkthrough

Added a --wait=all flag to the minikube startup configuration in the dev cluster YAML file. This ensures all startup processes complete before proceeding.

Changes

Cohort / File(s)	Summary
Minikube Configuration dev/cluster.yaml	Added --wait=all flag to minikube.startFlags to wait for all startup processes to complete.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description provides context about the change but is incomplete, missing the required 'Type of change' checkboxes, 'How should this be tested?' section, and most checklist items from the template.	Complete the PR description by adding the 'Type of change' section with appropriate checkboxes, detailed testing instructions, and the required/appreciated checklist items.
Title check	❓ Inconclusive	The title mentions 'cillium policy' and 'CRDs' which aligns with the PR objectives, but the actual changeset only adds '--wait=all' to minikube startup flags in dev/cluster.yaml.	Clarify if the title should reflect the actual change (minikube startup flag) or if additional changes addressing CRD/policy retry logic are missing from this changeset.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-cillium-policy

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

dev/cluster.yaml (1)

6-14: Consider adding --wait-timeout to prevent indefinite blocking.

The --wait=all flag waits for all cluster components to be ready. To ensure dev/CI doesn't hang if a component fails to become ready, consider explicitly setting --wait-timeout (e.g., --wait-timeout=10m) alongside --wait=all.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@dev/cluster.yaml` around lines 6 - 14, Add an explicit wait timeout so the
startFlags entry that currently contains "--wait=all" cannot block indefinitely:
add a sibling list entry like "--wait-timeout=10m" under startFlags (alongside
"--wait=all") and ensure it follows the same quoting/indentation as the other
flags; update any related CI/dev docs or env that assume indefinite wait if
needed.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@dev/cluster.yaml`:
- Around line 6-14: Add an explicit wait timeout so the startFlags entry that
currently contains "--wait=all" cannot block indefinitely: add a sibling list
entry like "--wait-timeout=10m" under startFlags (alongside "--wait=all") and
ensure it follows the same quoting/indentation as the other flags; update any
related CI/dev docs or env that assume indefinite wait if needed.