kubectl component (Go lane)

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, kubernetes
Domain
cli, devops, networking

Research direction

Start with clis/kubectl.toml and the existing setup-gh-sandbox pattern, then review the Go-wasip3 fork gaps noted in the issue. Run kubectl version --client and a real get against a cluster using kubeconfig, CA certificates, and DNS. Done means the component builds through the Go lane and both checks work, with any vendor patch or fork limitation recorded.

Written by the indexing model from the issue text.

Description

enhancement gh-demo

Build kubectl as a component — 231 uses. It's a Go CLI, so it rides the
proven Go lane that already produces gh, and it's networked (HTTPS to the
API server) like gh.

Tasks
  • clis/kubectl.toml (Go lane, pinned tag) + vendor patch if needed.
  • Sandbox: kubeconfig + CA certs + DNS (reuse the setup-gh-sandbox pattern).
  • Run kubectl version --client, then a real get against a cluster.
  • Note Go-wasip3 fork gaps (same toolchain as gh/gcx).

Part of #84.

Dominant language
Rust
Stars
9
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sd2k/conch

All issues in sd2k/conch

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.