When to select this tool over K9s?

Open
#213 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, rust
Domain
cli, documentation

Research direction

The issue mentions this Rust Kubernetes CLI and K9s, but names no files, tests, or entry points. Start by reviewing the tool's existing documentation and commands, then define the comparison's scope; done means documenting when users should choose this tool over K9s.

Written by the indexing model from the issue text.

Description

Being a K9s user for more than a year, I wanted to understand what extra this tool brings to the table.

Dominant language
Rust
Stars
1.5k
Forks
93
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 databricks/click

All issues in databricks/click

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.