Add kubectl-create-limitrange plugin to Krew index

[mfenerich]

Title: Add kubectl-create-limitrange plugin to Krew index
Description:
This PR adds the kubectl-create-limitrange plugin to the Krew plugin index.
Plugin Name: kubectl-create-limitrange
Plugin Repository: https://github.com/mfenerich/kubectl-lr

Overview

kubectl create-limitrange is a kubectl plugin that extends the standard kubectl create command, allowing easy creation of LimitRange resources in Kubernetes namespaces with configurable CPU and memory limits. It helps cluster administrators enforce resource constraints and optimize cluster performance.

Key Features

• Easy Creation of LimitRanges: Streamlines the process of creating LimitRange resources without the need to write YAML manifests manually.
• Configurable Resource Limits: Allows users to specify minimum and maximum CPU and memory limits according to their requirements.
• Namespace Support: Can target specific namespaces, making it flexible for multi-tenant environments.
• Cross-Platform Availability: Binaries are available for macOS (darwin), Linux, and Windows on amd64 architectures.

Why This Plugin Should Be Accepted

• Enhances Productivity: Automates repetitive tasks, saving time and reducing the potential for human error in resource configuration.
• Promotes Best Practices: Encourages the use of LimitRanges, which are essential for resource management and ensuring fair resource allocation among pods.
• Community Benefit: Fills a gap in the current plugin ecosystem by providing a dedicated tool for managing LimitRanges.
• Follows kubectl Conventions: Uses the standard verb-noun pattern (create limitrange) that aligns with kubectl's command structure.

Compliance with Krew Guidelines

• Manifest Validation: The plugin manifest has been validated and complies with Krew's plugin manifest specification.
• License: The plugin is open-sourced under the Apache License 2.0, aligning with Krew's licensing requirements.
• Naming Convention: The plugin name follows the kubectl-<verb>-<noun> format, adhering to kubectl's command structure.

Testing and Verification

• Installation: Successfully tested installation via Krew on macOS and Linux systems.
• Functionality: Verified that the plugin correctly creates LimitRange resources with specified CPU and memory limits.
• Documentation: Usage instructions and examples are provided in the plugin's README.

Example Usage

# Create a LimitRange in the 'development' namespace with custom limits
kubectl create limitrange my-limitrange --namespace=development --min-cpu=100m --max-cpu=500m --min-memory=128Mi --max-memory=1Gi

Related Links

• Plugin Homepage: https://github.com/mfenerich/kubectl-lr
• Documentation: [README.md](https://github.com/mfenerich/kubectl-lr/blob/main/README.md)
• Kubernetes LimitRange Docs: [Limit Ranges](https://kubernetes.io/docs/concepts/policy/limit-range/)

[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

[mfenerich]

Hi @chriskim06 or team,

Just a friendly reminder about this PR – it’s been open for a while, and I’d appreciate it if someone could take a look when time permits. Let me know if there’s anything I can clarify or improve!

Thanks for your time! 😊

[ahmetb]

Hey! I'm thinking if we should accept this as part of the new "create plugins" feature (would be named "create-limitrange" in that case).

We can implement that feature fairly easily and users can call it via "kubectl create limitrange".

[mfenerich]

Hey, any think I could help with, @ahmetb @chrischdi ?

[chrischdi]

Hey, any think I could help with, @ahmetb @chrischdi ?

I was probably tagged by accident, I don't have any permissions/ownerships on this repository :-)

Did you consider ahmetb's question?

[mfenerich]

Sorry, I meant @chriskim06... Thanks, man

[chriskim06]

whoops sorry, i totally missed this notification the first time around. but as @chrischdi said, have you considered @ahmetb's question? i agree this would make more sense as a create plugin. kubectl create limitrange seems better than kubectl limitrange create limitrange. we'd have to make some changes like ahmet mentioned (not entirely sure what they would need to be off the top of my head; and i think there would need to be some sort of change to how we inform users of what plugins are normal vs create plugins)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfenerich
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.

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

[mfenerich]

Hey, guys... I think I get it done as @ahmetb suggested.

When you have some time pls review this PR :)

Thank you, @chriskim06