* Feat: Move shell pod cluster config to general config
> BREAKING CHANGE! K9s configuration breaking change! Shellpod specification will
no longer reside with a cluster configuration. It is now part of the
global K9s configuration object.
Shellpod configuration should be part of k9s config. Clusters admins
will most likely use the same image and config to run shells on their
nodes. Each cluster in turn will have the option to either
enable/disable shelling into nodes. This not only DRYs up the k9s config
but also allows user to consolidate their shell pod configuration in one
central place.
* Fix#2290 - Add freebsd assets
* Maintenance cleaning up
* Fix#2166 - Add taint tracking column to node view
* Fix#2009: Update screendump file names to contain resource info
* Maintenance: Cleanup errror messages
* Fix#1513: Change log default to tail vs last 5min
* Fix#2166: Add taint indicator on node view
* Fix#2165: Track init co restarts
* Fix#2308: Fix rbac auth checks
* Fix#2036: Fix npe on filtering CRDs
* Fix#2219: Turn on TTY option on shellpod
* Fix#2167: Update color escape sequence on copy
* Fix#2297: Enable multi select on nodes
* Cleanup headers
* Fix#2162: Allow edit when describing/viewing
* Feat: Add helm release history support
* Fix#2039: Command Arrow up/down + enter support
* Small refactor
* Add img vulenerability scans support
* Change skin loading and support
- Move skin specification to k9s cluster config section
- Load skins for skins dir
* Release v0.29.0 docs
The original check in ScanSA assumed the service account on the pod spec
was not blank. It can be blank and when it is kubernetes will default
to using the 'default' service account. This change extends the check
logic to also include that.
When checking permissions to (un)suspend cronjobs, a user will always be
considered as unauthorized, because of the wrong arguments order when
calling the `CanI` function.
For `CanI` definition, see:
2f72441bac/internal/client/client.go (L138)
```
func (a *APIClient) CanI(ns, gvr string, verbs []string) (auth bool, err error)
```
* Update CronJob version to v1 (from v1beta1, unavaliable from 1.25 onwards).
* Try both batch/v1beta1 (for legacy) and batch/v1
* Revert previous commit. Use c.GVR() to find the correct version. Make
cronjob (un)suspend version aware.
* Simply changes by dropping support for deprecated batch/v1beta1 version
add toggleSuspend action and remove separate suspend/unsuspend
Allow to toggleSuspend on one resource only and update text
fix showSuspendDialog
Co-authored-by: Ludovico Russo <ludovico.russo@redcarbon.ai>
Fernand Galiana
SammyA
Dan Ramich
Samuel Demirdjian
Aleksei Romanenko
Ludovico Russo
Steffen Krause