Skip to content

feat(local): add kiac backend for Apple silicon clusters - #88

Open
patrickleet wants to merge 1 commit into
mainfrom
feat/kiac-backend
Open

feat(local): add kiac backend for Apple silicon clusters#88
patrickleet wants to merge 1 commit into
mainfrom
feat/kiac-backend

Conversation

@patrickleet

Copy link
Copy Markdown
Collaborator

Summary

  • New hops local backend kiac (saiyam1814/kiac): Kubernetes nodes as lightweight VMs on apple/container (Apple silicon).
  • Cluster name hops → kube context kiac-hops (kubeadm single-node).
  • Registry wiring via containerd certs.d (same model as kind).
  • When Mac cannot reach the node IP (vmnet / Local Network), hops starts hops-kiac-api-proxy on 127.0.0.1:16443 and rewrites kubeconfig.
  • Documents apple/container 1.1.0 preference until kiac#14 (1.2.x sysctl ip_forward break).

Verified locally

  • cargo test --bin hops-cli backend (40 tests)
  • hops local start --backend kiac on this Mac: Crossplane + providers + HTTPS registry ready; context kiac-hops via localhost proxy.

Usage

# Prefer container 1.1.0 until kiac#14 is fixed
brew tap saiyam1814/tap && brew install saiyam1814/tap/kiac
hops local start --backend kiac
kubectl get nodes   # context kiac-hops

Test plan

  • hops local install --backend kiac on a clean Mac
  • hops local start --backend kiac (create + resume paths)
  • hops local doctor --backend kiac
  • hops local destroy --backend kiac
  • Path config install if host can reach NodePort 30500

Wire hops local to saiyam1814/kiac (apple/container VMs): create/resume
single-node kubeadm cluster hops, containerd registry certs.d, and a
localhost API proxy when Mac→node IP is unreachable. Document container
1.1.0 pin until kiac#14 (sysctl on 1.2.x).
@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@patrickleet, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1c7076fe-87e8-4ed1-b4ce-5e932bbdfff8

📥 Commits

Reviewing files that changed from the base of the PR and between 78c0fef and dfbd2a0.

📒 Files selected for processing (4)
  • README.md
  • src/commands/local/backend/kiac.rs
  • src/commands/local/backend/mod.rs
  • src/commands/local/mod.rs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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