https://github.com/gabeduke/kubectl-iget
Kubectl plugin to interactively get and filter kubernetes objects
https://github.com/gabeduke/kubectl-iget
Last synced: 6 months ago
JSON representation
Kubectl plugin to interactively get and filter kubernetes objects
- Host: GitHub
- URL: https://github.com/gabeduke/kubectl-iget
- Owner: gabeduke
- License: other
- Created: 2024-01-29T04:27:16.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-31T03:40:23.000Z (over 2 years ago)
- Last Synced: 2024-06-19T20:58:21.319Z (about 2 years ago)
- Language: Go
- Size: 22.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Kubectl Interactive Get (kubectl-iget) Plugin
## Overview
`kubectl-iget` is an interactive Kubernetes CLI plugin that extends the functionality of `kubectl get`. It allows users to interactively construct object selectors and filters for Kubernetes objects, enhancing the experience of querying Kubernetes resources.
## Features
- **Drop-In Replacement for `kubectl get`**: Use `kubectl iget` just like you would use `kubectl get`.
- **Interactive Selection and Filtering**: Dynamically build selectors and filters for Kubernetes objects through an interactive CLI interface.
- **Support for Various Kubernetes Objects**: Works with standard Kubernetes objects and CRDs.
- **Customizable Queries**: Tailor your queries with command-line arguments and interactive selections.
## Getting Started
Install the plugin and use it as a replacement for `kubectl get`. For example:
```bash
kubectl iget pods -l app= -n
```
## Getting Started
(TODO: Installation instructions, basic usage, etc.)
## Usage
Use `kubectl iget` followed by the Kubernetes object type and any additional `kubectl get` flags you normally use. The interactive interface will then guide you through further refining your query.
### Basic Example
```bash
kubectl iget pods -l app=myapp -n mynamespace
```
### Advanced Features
(TODO: Describe advanced features like the dry-run option and potential future features.)
## Contributing
Contributions to the project are welcome! Please refer to the contributing guidelines for more information.
## License
(TODO: Specify the license.)
## Acknowledgements
(TODO: Acknowledge any contributors, inspirations, or significant dependencies.)