Verified 2026-09-13 against the live krew-index.
What is wrong
kubectl krew install kq cannot work today. The plugin manifest is absent from krew-index:
https://raw.githubusercontent.com/kubernetes-sigs/krew-index/master/plugins/kq.yaml -> 404- krew-index carries 407 plugins; none matches
kq, kube-intel or kubeintellect
- No krew-index PR has ever been opened from
MSKazemi (gh pr list --repo kubernetes-sigs/krew-index --author MSKazemi --state all returns empty)
Why this is worth an issue
v2.3.1 exists for exactly this purpose. Its release notes say it is a "Patch release so kubectl kq actually reaches krew-index", and explain that v2.3.0 shipped a .krew.yaml whose addURIAndSha call was indented two levels too deep for krew-release-bot to render. The indentation was fixed and released — but the plugin still never landed, so the failure is somewhere after that fix.
Both halves of the machinery are present in the tree: .krew.yaml and .github/workflows/krew.yml.
Scope
Find out why the release path does not reach krew-index and either land the plugin or stop advertising the channel.
- Read the
krew.yml run for the v2.3.1 and v2.5.0 tags — did it execute, did it succeed, did it attempt a PR?
- Common causes worth ruling out: krew-release-bot needs the workflow to run on
release: published (not push: tags); it needs a token with permission to open a PR on the fork; and the manifest must pass krew-index validation.
- If it cannot be automated, open the krew-index PR by hand once and document the manual step.
Acceptance criteria
kubectl krew install kq succeeds from a clean machine against upstream krew-index, or- the krew channel is removed from the release notes and any docs that mention it, so nothing advertises an install path that does not exist.
Exposure
Limited. grep finds no krew mention in README.md or docs/, so the claim currently lives only in the v2.3.0 and v2.3.1 release notes. That is the same bug class as #151 (a documented flag that did not work): a wrong install command costs the reader trust rather than a search.
Verified 2026-09-13 against the live krew-index.
What is wrong
kubectl krew install kqcannot work today. The plugin manifest is absent from krew-index:https://raw.githubusercontent.com/kubernetes-sigs/krew-index/master/plugins/kq.yaml-> 404kq,kube-intelorkubeintellectMSKazemi(gh pr list --repo kubernetes-sigs/krew-index --author MSKazemi --state allreturns empty)Why this is worth an issue
v2.3.1exists for exactly this purpose. Its release notes say it is a "Patch release sokubectl kqactually reaches krew-index", and explain thatv2.3.0shipped a.krew.yamlwhoseaddURIAndShacall was indented two levels too deep for krew-release-bot to render. The indentation was fixed and released — but the plugin still never landed, so the failure is somewhere after that fix.Both halves of the machinery are present in the tree:
.krew.yamland.github/workflows/krew.yml.Scope
Find out why the release path does not reach krew-index and either land the plugin or stop advertising the channel.
krew.ymlrun for thev2.3.1andv2.5.0tags — did it execute, did it succeed, did it attempt a PR?release: published(notpush: tags); it needs a token with permission to open a PR on the fork; and the manifest must passkrew-indexvalidation.Acceptance criteria
kubectl krew install kqsucceeds from a clean machine against upstream krew-index, orExposure
Limited.
grepfinds no krew mention inREADME.mdordocs/, so the claim currently lives only in thev2.3.0andv2.3.1release notes. That is the same bug class as #151 (a documented flag that did not work): a wrong install command costs the reader trust rather than a search.