hey krew-index team,

I am krew-release-bot, and I would like to open this PR to publish version v0.37.1 of virt on behalf of @kubevirt-bot.

Thanks, @krew-release-bot

<!--

PLUGIN DEVELOPERS: If you are submitting a new plugin

• Make sure you read the Plugin Naming Guide: https://krew.sigs.k8s.io/docs/developer-guide/develop/naming-guide/
• Verify you can install your plugin locally: kubectl krew install --manifest=[...] --archive=[...]

-->

Apologies, I thought I merged this.

I think we should remove this for now until we figure out what the issue is

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/993#issuecomment-765075206" title="Approved">ahmetb</a>, <a href="https://github.com/kubernetes-sigs/krew-index/pull/993#" title="Author self-approved">chriskim06</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [ahmetb,chriskim06]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

/lgtm /approve

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/993#" title="Author self-approved">chriskim06</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [chriskim06]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/992#issuecomment-765019353" title="Approved">ahmetb</a>, <a href="https://github.com/kubernetes-sigs/krew-index/pull/992#" title="Author self-approved">krew-release-bot</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [ahmetb]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

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

This pull request seems to straightforward. I'll go ahead and accept it. :+1: Cheers.

/lgtm /approve

hey krew-index team,

I am krew-release-bot, and I would like to open this PR to publish version v0.37.1 of virt on behalf of @kubevirt-bot.

Thanks, @krew-release-bot

Kindly ping @ahmetb, is this good to merge?

Also, please consider setting up Krew release automation which helps you skip manually making updates to your Krew manifests on each new version and send a pull request. It’s a GitHub workflow bot that can run every time you push a new tag. Those PRs are automatically approved.

I want to introduce a new kubectl plugin "kubectl-skew" (https://github.com/dty1er/kubectl-skew). This is a simple plugin to show if the user's kubernets cluster/kubectl version is "skewed" (= not following Kubernetes version skew policy).

Some kubernetes users (especially beginners) get confused by kubectl or kubernetes behavior which looks weird. They might be a actual bug, but some of them are caused by their version. Because kubernetes development is fast, sometimes using inappropriate version causes such confusion.

What I want to do are:

• Help people to be aware of "version skew policy" (I've found some people even don't know it)
• Help people to understand if they are "skewed" or not easily

I believe this plugin is useful for such situation and be worth to be indexed in krew central repository.

• The result of kubectl krew install on my laptop

~/repos/src/github.com/dty1er/krew-index add-skew $ kubectl krew install --manifest=./plugins/skew.yaml --archive=./tmp/kubectl-skew_0.0.3_Linux_x86_64.tar.gz
Installing plugin: skew
Installed plugin: skew
\
 | Use this plugin:
 |      kubectl skew
 | Documentation:
 |      https://github.com/dty1er/kubectl-skew
/

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/991#issuecomment-764427558" title="Approved">ahmetb</a>, <a href="https://github.com/kubernetes-sigs/krew-index/pull/991#" title="Author self-approved">dty1er</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [ahmetb]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

/lgtm /approve NB: manually merging due to infra issue in CI pipine.

@ahmetb Thank you for your advices. I fixed them to look better. Can you take a look again.

A few cosmetic issues. It really works fine for me. Testing system is throwing some error that started to occur today. It's not related to you.

might be good to link to the skew policy here

Instead of starting as

"kubectl skew" shows

you can just say:

This plugin checks

or

This plugin shows

You can shorten as:

Find if your cluster/kubectl version is skewed

or

Check skew status of your cluster/kubectl version

these comments are redundant

Hmm it seems like the CI is failing because of flakiness?

tee: /dev/stderr: No such device or address

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/991#" title="Author self-approved">dty1er</a> To complete the pull request process, please assign ahmetb after the PR has been reviewed. You can assign the PR to them by writing /assign @ahmetb in a comment when ready.

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

<details open> 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 </details> <!-- META={"approvers":["ahmetb"]} -->

Welcome @dty1er! <br><br>It looks like this is your first PR to <a href='https://github.com/kubernetes-sigs/krew-index'>kubernetes-sigs/krew-index</a> 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval. <br><br>You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation. <br><br>You can also check if kubernetes-sigs/krew-index has its own contribution guidelines. <br><br>You may want to refer to our testing guide if you run into trouble with your tests not passing. <br><br>If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs! <br><br>Thank you, and welcome to Kubernetes. :smiley:

I want to introduce a new kubectl plugin "kubectl-skew" (https://github.com/dty1er/kubectl-skew). This is a simple plugin to show if the user's kubernets cluster/kubectl version is "skewed" (= not following Kubernetes version skew policy).

Some kubernetes users (especially beginners) get confused by kubectl or kubernetes behavior which looks weird. They might be a actual bug, but some of them are caused by their version. Because kubernetes development is fast, sometimes using inappropriate version causes such confusion.

What I want to do are:

• Help people to be aware of "version skew policy" (I've found some people even don't know it)
• Help people to understand if they are "skewed" or not easily

I believe this plugin is useful for such situation and be worth to be indexed in krew central repository.

• The result of kubectl krew install on my laptop

~/repos/src/github.com/dty1er/krew-index add-skew $ kubectl krew install --manifest=./plugins/skew.yaml --archive=./tmp/kubectl-skew_0.0.3_Linux_x86_64.tar.gz
Installing plugin: skew
Installed plugin: skew
\
 | Use this plugin:
 |      kubectl skew
 | Documentation:
 |      https://github.com/dty1er/kubectl-skew
/

<!--

PLUGIN DEVELOPERS: If you are submitting a new plugin

-->

• [x] Make sure you read the Plugin Naming Guide: https://krew.sigs.k8s.io/docs/developer-guide/develop/naming-guide/
• [x] Verify you can install your plugin locally: kubectl krew install --manifest=[...] --archive=[...]

Below is the test output:

➜  krew-index git:(add-ks) ✗ kubectl krew install --manifest plugins/ks.yaml
WARNING: To be able to run kubectl plugins, you need to add
the following to your ~/.zshrc:

    export PATH="${PATH}:${HOME}/.krew/bin"

and restart your shell.

Installing plugin: ks
Installed plugin: ks
\
 | Use this plugin:
 | 	kubectl ks
 | Documentation:
 | 	https://github.com/linuxsuren/ks
/

Try to fix the CLA issue with #951