* correct describe of helm history
* value, yaml and describe view for helm-history
* add value_extender and clean up code
* move showValues to the new extender
* 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
At the time of making this commit, the package `github.com/ghodss/yaml`
is no longer actively maintained.
`sigs.k8s.io/yaml` is a permanent fork of `ghodss/yaml` and is actively
maintained by Kubernetes SIG.
Signed-off-by: Eng Zer Jun <engzerjun@gmail.com>
* check for plausible overflow when seting up env
* Various fixes and clean up
* Introduce File transfer command
- Add ability to upload/download files from/to pods
* release v0.28.0
* Switch to new default-container pod annotation
kubectl.kubernetes.io/default-logs-container has been deprecated and
removed in kubectl, see
3a9c6f2a2f
* Show the default container as the first entry
In container selections show the default container as the first entry of
the list.
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.
* bugfix for port forward costum containers not showing
#1844
* Adjust the port forward test key structure
Co-authored-by: Eugene <eugene.berger@dell.com>
Add the same policy view to ServiceAccounts as users/groups.
This also works under the xray view. This commit also fixes the
issue with role/rolebindings not having the same name not showing
up in Policy view.
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
* Fix path when viewing ScreenDump
* Log save should use `CurrentCluster` iso `CurrentContext`
* Remove sanitizing of dir in ScreenDump dao
* Switch `CurrentCluster` to `CurrentContext` for SD
* Revert log saving to `CurrentContext`
* Save tables to `CurrentContext` iso `CurrentCluster`
On second thought, I'll accept your PR and will update the code to use `all` as I am getting ready for a new drop and would like to include your changes. Thanks Anthony!
`var x int64` means the value is 0 rather than the intended nil
(default).
`Delete` doesn't provide a way to configure the grace period anyway so
remove the variable and only override on a `force`
Co-authored-by: Phil Kates <phil.kates@cartacapitalmarkets.com>
Fernand Galiana
Adam Sranko
Alexandru Placinta
Joshua Ward
Jayson Wang
Nick Mills-Barrett
Takumi Sue
Eng Zer Jun
Mike
Felix Geyer
Vlad Fratila
guangwu
SammyA
Dan Ramich
Eugene Berger
Samuel Demirdjian
fredericvl
Richard Hull
Anthony
Phil Kates
Aleksei Romanenko