Update the spy plugin to exclusively support containerd.

[asaf400]

I have create a fork of kubespy | krew index that was vibe coded to support k8s clusters running containerd 📦 (and possibly cri-o ❄️ )

Fork

The existing kubespy is non functional on modern clusters, but I did not want to overwrite it's name..

[ahmetb]

🤖 Beep beep! I’m a robot speaking on behalf of @ahmetb. 🤖

---

Thanks for submitting your kubectl plugin to Krew!
One of the krew-index maintainers will review it soon. Note that the reviews for new plugin submissions may take a few days.

In the meanwhile, here are a few tips to make your plugin manifest better:

• Make sure your plugin follows the best practices.
• Eliminate redundant wording form shortDescription (it should be max 50 characters).
• Try to word wrap your description to 80-character lines (no usage examples, please).

Thanks for your patience!
/kind new-plugin

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: asaf400 / name: Asaf Levy (d8a1d84, 09863fa, 38f96f9, 48bb54b)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: asaf400
Once this PR has been reviewed and has the lgtm label, please assign chriskim06 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ahmetb]

Have you asked author to bless your fork so you don't have to call it spy2?

We typically don't accept fork graphs, and you can still distribute your fork via Krew using custom indexes: https://krew.sigs.k8s.io/docs/developer-guide/custom-indexes/ That way users can still install your plugin via Krew, but they'll be downloading the plugin manifest from your repository instead of krew-index.

[ahmetb]

Let me know if you can get a hold of the current author. That would be great if they give you a blessing and we can switch to your fork instead.

You can still distribute your plugin via Krew using custom indexes: https://krew.sigs.k8s.io/docs/developer-guide/custom-indexes/ That way users can still install your plugin via Krew, but they'll be downloading the plugin manifest from your repository instead of krew-index.

/hold

[asaf400]

Sorry for the late reply, I did not mean to have this become stale, I will try and reach out and update here, I haven't done that yet, since I was busy with critical work.

…

On Mon, 23 Mar 2026, 00:53 Ahmet Alp Balkan, ***@***.***> wrote: *ahmetb* left a comment (kubernetes-sigs/krew-index#5196) <#5196 (comment)> Let me know if you can get a hold of the current author. That would be great if they give you a blessing and we can switch to your fork instead. You can still distribute your plugin via Krew using custom indexes: https://krew.sigs.k8s.io/docs/developer-guide/custom-indexes/ That way users can still install your plugin via Krew, but they'll be downloading the plugin manifest from your repository instead of krew-index. — Reply to this email directly, view it on GitHub <#5196?email_source=notifications&email_token=ADMDHLRTXZCQ7GRUK3N3BCT4SBVHJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQG4YTIOJRGUZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4107149152>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADMDHLV4J75MDDE2LOTYHG34SBVHJAVCNFSM6AAAAACRY3CEUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBXGE2DSMJVGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>