* feat: enhance table column selection and sorting functionality
* fix: update key binding for sorting selected column to Ctrl+O
* remove unused setSelectedColIdx method and sortIndicator function
* test: update expected hints count in various view tests
* test: update expected hints count in TestServiceNew
* fix: update keyboard handling for column selection to use Shift key
* refactor: streamline column selection logic and initialize selected column based on current sort
* fix: change key binding for sorting selected column from Ctrl+O to Shift+S
* test: update expected hints count in help, namespace, pod, and PVC tests
* fix#3455
* Clean up and refactor
* fix#3495#3470#3455 - fix cmd alias and filters
* fix#3535 - revert
* fix#3478 - make vulscan a bit less cpu extensive (init stab...)
* fix issue with plugin foreground exit
* fix#3466-add shared gpu on nodes
* fix#3541 - use default namespace when not specified
* update deps + release notes
* Add delete functionality for Kubernetes contexts
This adds the ability to delete Kubernetes contexts using the 'd' key in the context view. The implementation includes:
- New delete command bound to 'd' key
- Confirmation dialog before deletion
- Error handling and UI refresh after deletion
* Refactor context delete dialog to use standard dialog component
- Replace custom delete confirmation with dialog.ShowConfirm
- Add read-only mode checks for rename and delete commands
- Change delete keybinding from 'd' to 'Ctrl+d'
- Remove unused deletePage constant and related functions
- Simplify delete callback logic
* Refactor context view key bindings to separate dangerous operations
* Fix linting error
* refactor: change refreshRate type to float64 for improved precision
* test: update assertions for refreshRate to use assert.InDelta for precision
* refactor: enforce minimum refresh rate and update related tests
* refactor: change refresh rate type to float32 and update related logic
* refactor: update refresh rate validation and logging in GetRefreshRate method
* refactor: update logging keys for refresh rate validation in GetRefreshRate method
Issue: when calling exec / attach on a pod with sidecar containers or ephemeral containers, those are not presented as potential targets to exec / attach / transfer.
Proposed solution: the method fetchContainers is only called with allContainers=false to find containers we can exec / attach / transfer.
Both ephemeral containers and sidecar init containers could be used in this case however with the current behavior they're not shown.
I'm proposing to change the behavior of the method to return any sidecar container and ephemeral container when called with allContainers=false since there is no other caller using that parameter set to false, so we won't break other call sites
* Update deprecated yaml.v2->v3
* [Fix] fix issue with yaml sanitization when [] or [xxx] are present
* Spring cleanup
* fix#3192
* Column Blow Reloaded
* Add ability to use alias when specifying custom views
Currently, running the cronjob trigger command supports
triggering the currently selected cronjob only. It would
be nice if this feature supported triggering all marked
cronjobs in the case that there are marked cronjobs - in
a similar fashion to scaling deployments or generally
deleting resources.
Let's modify cronjob triggering to support the case where
the user has marked multiple cronjobs in the cronjob view.
Fixes#3166
Throughout the code, pushCmd is used for when a command is being executed (switched to) to conditionally add the new command onto the history. The history commands (keybinds `[`, `]`, `-`) only navigate through the stack with indices and therefore should never manipulate the stack -- however with some special commands (specialCmd), navigating to those commands previously unconditionally added the command to the stack unlike "typical" commands like `pods`, `svc`.
Here we pass in the pushCmd boolean to all appropriate special commands so that if the stack should not be manipulated, they do not push their command onto the stack.
The original issue reported issues with Aliases, but there were unreported bugs with Namespaces and Contexts as well. Notably, RBAC commands and Dir commands were not modified as they do not push their command onto the history stack, functioning more as "virtual" commands that will not appear in the history.
* fix#3119 - non alpha cust col
* Address issues:
o fix#3118 - wrong res shown on alias
o fix#3120 - shuffled cols after sort
* fix#3122 - view event not sorted
* rel v0.40.4
* feat(app): add Go Back and Last View
Go Back walks back through the history until at the oldest saved view
Last View switches between the current and previous views like how "cd -" works
* feat(history): add keyboard shortcuts to navigate history
* fix(tests): fix history/app tests
* docs(README): update history and last command navigation info
* fix(internal): add missing parameter
* feat(help): add history keybinds
* fix(help): adjust capitalization for history commands
* docs(readme): fix typo
Co-authored-by: merusso <merusso@gmail.com>
---------
Co-authored-by: merusso <merusso@gmail.com>
Tatsuya Kyushima
Ümüt Özalp
Artem Yadelskyi
SebPlv
Fernand Galiana
henry
Maico Timmerman
Alex Cantu
yingshanghuangqiao
jfremy-openai
Rudrakh Panigrahi
tscuite
Sunggun Yu
Jason Tackaberry
Erich Fussi
DanCocking
tyzbit
Clément Rezvoy
rhslack
Jayson Wang