add kubectl-lr manisfest

[mfenerich]

Title: Add kubectl-lr plugin to Krew index

Description:

This PR adds the kubectl-limitrange plugin to the Krew plugin index.

Plugin Name: kubectl-limitrange

Plugin Repository: https://github.com/mfenerich/kubectl-lr

Overview

kubectl-limitrange is a kubectl plugin that simplifies the creation of LimitRange resources in Kubernetes namespaces. It provides an easy and efficient way to set CPU and memory limits, helping 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.

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-<plugin-name> format, adhering to the recommended naming conventions.

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 lr create limitrange --cpu-min=100m --cpu-max=500m --memory-min=128Mi --memory-max=1Gi

Related Links

• Plugin Homepage: https://github.com/mfenerich/kubectl-lr
• Documentation: README.md
• Kubernetes LimitRange Docs: Limit Ranges

[linux-foundation-easycla]

• ✅login: mfenerich / (856fcb9)

The committers listed above are authorized under a signed CLA.

[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: mfenerich
Once this PR has been reviewed and has the lgtm label, please assign ahmetb for approval. For more information see the Kubernetes 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

[k8s-ci-robot]

Welcome @mfenerich!

It looks like this is your first PR to kubernetes-sigs/krew-index 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

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.

You can also check if kubernetes-sigs/krew-index has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

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!

Thank you, and welcome to Kubernetes. 😃