✨ feat: Added kubectl-mscale

[Stenstromen]

Please review my plugin submission

[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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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]

There are quite a few plugins that support running across multiple namespaces/context at a time in krew-index. We likely wouldn't accept a plugin for just running a specific command across multiple namespaces.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Stenstromen]

/remove-lifecycle stale

[ahmetb]

Sorry this plugin still does not make a ton of sense to me. krew-index is a curated index and if a plugin's value add is easily achievable by composing existing tools, we typically don't accept it to krew-index.

In this case, the plugin is too specific to running a specific sub-command across multiple namespaces which is achievable in a for loop or xargs/parallel, and is not adding much value beyond that?