Releases: derailed/k9s
v0.30.6
Release v0.30.6
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
Thank you all for pitching in and helping flesh out issues!!
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2401 Context completion broken with mixed case context names
- #2400 Panic on start if dns lookup fails
- #2387 Invalid namespace xxx - with feelings??
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.5
Release v0.30.5
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
Thank you all for pitching in and helping flesh out issues!!
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2394 Allow setting custom log dir
- #2393 When switching contexts k9s does not switching to cluster's pod/namespaces/other k8s kinds view
- #2387 Invalid namespace xxx - with feelings!
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
- #2396 feat: allow to customize logs dir through environment variable
- #2395 fix: create user tmp directory before the app one
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.4
Release v0.30.4
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
Thank you all for pitching in and helping flesh out issues!!
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2391 Version 0.30.* has issues with : chars in the cluster names from AWS
- #2397 Error: invalid namespace xxx
- #2389 Mixed-case named contexts cannot be switched to from contexts view
- #2382 Header always shows Cluster from kubeconfig current-context
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
- #2390 case sensitive for specific command args and flags
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.3
Release v0.30.3
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
🎵 On The twelfth day of Christmas my true love gave to me... More Bugs!! 🎵
Thank you all for pitching in and help flesh out issues!!
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2379 Filtering with equal sign (=) does not work in 0.30.X
- #2378 Logs directory not created in the k9s config/home dir 0.30.1
- #2377 Opening AWS EKS contexts create two directories per cluster 0.30.1
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.2
Release v0.30.2
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
🎵 On The eleventh day of Christmas my true love gave to me... More Bugs!! 🎵
Thank you all for pitching in and help flesh out bugs!!
[!!FEATURE NAME CHANGED!!] Vulnerability Scan Exclusions...
As it seems customary with all k9s new features, folks want to turn them off ;(
The Vulscan feature did not get out unscaped ;(
As it was rightfully so pointed out, you may want to opted out scans for images that you do not control.
Tho I think it might be a good idea to run wide open once in a while to see if your cluster has any holes??
For this reason, we've opted to intro an exclusion section under the image scan configuration to exclude certain images from the scans.
Here is a sample configuration:
k9s:
liveViewAutoRefresh: false
refreshRate: 2
ui:
enableMouse: false
headless: false
logoless: false
crumbsless: false
noIcons: false
imageScans:
enable: true
# MOTE!! Field Name changed!!
exclusions:
# Skip scans on these namespaces
namespaces:
- ns-1
- ns-2
# Skip scans for pods matching these labels
labels:
- app:
- fred
- blee
- duh
- env:
- devVideos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2374 The headless parameter does not function properly (v0.30.1)
- #2372 Unable to set default resource to load (v0.30.1)
- #2371 --write cli option does not work (0.30.X)
- #2370 Wrong list of pods on node (0.30.X)
- #2362 blackList: Use inclusive language alternatives
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
- #2375 get node filtering params from matching context values
- #2373 fix command line flags not working
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.1
Release v0.30.1
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
🎄 Maintenance Release! 🎄
🎵 On The eleventh day of Christmas my true love gave to me... Bugs!! 🎵
Got to love the aftermath... Thank you all for pitch'in in and help flesh out bugs!! The gift that keeps on... giving?
🎅 Merry Christmas to all and Best wishes for the new year!!🧑🎄
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Resolved Issues
- #2368 Pod CPU and MEM columns are empty in 0.30.0
- #2367 k9s 0.30.0 issue loading plugins
- #2366 List pods of deployment is now impossible
- #2264 k9s 0.30.0 fields and values missed in action in the "namespace view"
- #2263 Default 0.30.0 default skin on macOS is no good
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
- #2360 adding cancelable launch prompts to NodeShell
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.30.0
Release v0.30.0
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
♫ Sounds Behind The Release ♭
Going back to the classics...
- Home For Christmas - Fats Domino
- Our Love - Al Jarreau
- Body And Soul - Louis Armstrong
- On The Dunes - Donald Fagen
- Ciao - Lucio Dalla
- Basin Street Blues - Louis Prima
A Word From Our Sponsors...
To all the good folks below that opted to pay it forward and join our sponsorship program, I salute you!!
Sponsorship cancellations since the last release: 5! 🥹
🎄 Feature Release! 🎄
🎅 Merry Christmas to all and Best wishes for the new year!!🧑🎄
Videos Are In The Can!
Please dial K9s Channel for up coming content...
Breaking Bad!
☢️ !!Prior to installing v0.30.0!! Please be sure to backup your k9s configs directories or move them somewhere safe!!
☢️ Please watch the v0.30.0 Sneak peek series (links below) for detailed information.
☢️ Most K9s configuration files have either split or changed location or names on this drop!!
We recommend moving your current k9s config dirs to another location and start k9s from scratch and let it create and initialize the various configs
to their new spec and location. You can then use your existing setup and patch with the new layout/spec.
As of v0.30.0 all config files now use the*.yamlextension. We did our best to update all the docs to match the new version.
If you find doc issues either file an issue or better yet submit a PR!
Some of you might say: You're on the roll their bud! Two breaking changes drops in a row!!
Per the wise words of my beloved Grand mama! One can't cook a decent meal without creating a mess!
Not to mention we're still at v0.x.y so Open season on breaking changes is very much in full effect.
Tho I have tested this drop quite a bit, there is a strong chance that I've broken some stuff.
The key here is to walk the fine line of improving k9s code base and features set with minimal impact to you.
As you know by now, I am committed to ease the pain and resolve issues quickly to get you all back up and running.
From the scope changes in this release, I would caution that this drop will likely break you!
If so, worry not! We will fix the duds so we are Happy as a Hippo once again.
There was a few issues with the way K9s persists it's configuration and various artifacts. So we rewrote it!
First and foremost all k9s related YAML resources, will now use the standard ".yaml" extension.
I think we've bloated the code checking for both extensions with no real actionable value!
As it stands the main K9s configuration config.yml will now be static. These settings are now readonly! All the dynamic configurations that K9s manages now live in a new directory aka clusters. The clusters directory manages your k8s cluster/context configurations. So things like active view, namespace, favorites, etc... now live in this directory. K9s configurations are still managed using either xdg XDG_CONFIG_HOME or you can set K9S_CONFIG_DIR to specify a your preferred k9s configs location. Also all config files will now use the ".yaml" extension vs ".yml"!!
So the main k9s configuration (static) now looks like this:
# $XDG_CONFIG_HOME/k9s/config.yaml
# File will be autogenerated will all the default fixins if not found in the config specification.
k9s:
liveViewAutoRefresh: false
refreshRate: 2
maxConnRetry: 5
readOnly: false
noExitOnCtrlC: false
ui: # NOTE! New level!!
enableMouse: false
headless: false
logoless: false
crumbsless: false
noIcons: false
skipLatestRevCheck: false
disablePodCounting: false
# ShellPod configuration applies to all your clusters
shellPod:
image: busybox:1.35.0
namespace: default
limits:
cpu: 100m
memory: 100Mi
# ImageScan config changed from v0.29.0!
imageScans:
enable: false
# Now figures exclusions ie blacklist namespaces or specific workload labels
blackList:
# Exclude the following namespaces for image vulscans!
namespaces:
- kube-system
- fred
# Exclude the following labels from image vulscans!
labels:
k8s-app:
- kindnet
- bozo
env:
- dev
logger:
tail: 100
buffer: 5000
sinceSeconds: -1
fullScreenLogs: false
textWrap: false
showTime: false
thresholds:
cpu:
critical: 90
warn: 70
memory:
critical: 90
warn: 70Next context specific configurations that are managed by you and k9s live in the XDG data directory
i.e $XDG_DATA_HOME/k9s/clusters or $K9S_CONFIG_DIR/clusters if the env var is set.
$XDG_DATA_HOME/k9s
// Clusters tracks visited kubeconfig cluster/contexts
├── clusters
│ ├── fred
│ │ └── bozo
│ │ └── config.yaml
│ ├── bozorg
│ │ ├── kind-bozo-1
│ │ │ └── config.yaml
│ │ ├── kind-bozo-2
│ │ │ └── config.yaml
│ │ └── kind-bozo-3
│ │ └── config.yaml
│ └── bumblebeetuna
│ └── blee
│ └── config.yaml
└── skins
├── black_and_wtf.yaml
├── dracula.yaml
├── in_the_navy.yml
├── ...
Now looking at a given context configuration i.e cluster-1/context-1/config.yaml
# $XDG_DATA_HOME/k9s/clusters/bumblebeetuna/blee/config.yaml
k9s:
cluster: bumblebeetuna
readOnly: false # [New!] you can now single out a given context and make it readonly. Woof!
skin: in_the_navy # [NEW!] you can also skin individual contexts. Woof Woof!
namespace:
active: all
lockFavorites: false
favorites:
- all
- kube-system
- default
view:
active: dp
featureGates:
nodeShell: false
portForwardAddress: localhostTransient artifacts ie k9s logs, screen-dumps, benchmarks etc now live in the state config dir.
$XDG_STATE_HOME/k9s
├── k9s.log # K9s log files
└── screen-dumps
└── bumblebeetuna # Screen dumps location for context blee
└── blee
└── deployments-kube-system-1703018199222861000.csv
If you get stuck or if my instructions are just clear as mud... k9s info is always your friend!!
I feel this is an improvement (tho I might be unanimous on this!) especially for folks dealing with multi-clusters or swapping out there kubeconfigs...
NOTE! Paint is still fresh on this deal. Proceed with caution and please help us flush this feature out!
Got Prompt?
In this drop, we've also gave the k9s command prompt aka :xxx some love.
You have the ability to specify filter directly in the prompt.
So for example, you can now run something like :po /fred to run pod view with a filter to just show pods containing fred. Likewise :po k8s-app=fred,env=blee to filter by labels.
And now for theKrampus special... you can see pods in a different context all together via :pod @ctx-2.
Finally you can combo and send the whole enchilada via :po k8s-app=fred /blee ns-1 @ctx-x
Did I mention with completion where applicable? Yes Please!!
Compliments of Jayson Wang. Be sure to thank him!!
Put these frequent flyers command in an alias and now you can nav your clusters with even more style!
All Is Love?
🎵 On The twentieth day of Christmas my true love gave to me... Ten worklords a-leaping??... 🎵
This is a feature reported by many of you and its (finally!) here. As of this drop, we intro the workload view aka wk which is similar to kubetcl get all. I was reluctant to intro it given the potential hazards on larger clusters but figured why not? YOLO. I think using it in combo with the prompt updates it could pack a serious punch to observe workload related artifacts.
The Black List...
As it seems customary with all k9s new features, folks want to turn them off ;(
The Vulscan feature did not get out unscaped ;(
As it was rightfully so pointed out, you may want to opted out scans for images that you do not control.
Tho I think it might be a good idea to run wide open once in a while to see if your cluster has any holes??
For this reason, we've opted to intro a blacklist section under the image scan configuration to exclude certain images from the scans.
Here is a sample configuration:
k9s:
liveViewAutoRefresh: false
refreshRate: 2
ui:
enableMouse: false
headless: false
logoless: false
...v0.29.1
Release v0.29.1
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
Maintenance Release
Resolved Issues
- #2330 Skins don't work v0.29.0
- #2329 New skin system in v0.29.0 doesn't work if you use different k8s context files
- #2327 [Bug] Item highlighting broke in v0.29.0
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0
v0.29.0
Release v0.29.0
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s!
I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev
and see if we're happier with some of the fixes!
If you've filed an issue please help me verify and close.
Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated!
Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey,
please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
♫ Sounds Behind The Release ♭
🦃 Happy (Belated!) ThanksGiving To All! 🦃
Hope you and yours had a wonderful holiday!!
Hopefully this drop won't be a cold turkey 😳
I'd like to take this opportunity to honor two very special folks:
These guys have been relentless in fishing out bugs, helping out with support and addressing issues, not to mention enduring my code! 🙀
They dedicate a lot of their time to make k9s better for all of us!
So if you happen to run into them live/virtual, please be sure to Thank them and give them a huge hug! 🤗
I am thankful for all of you for being kind, patient, understanding and one of the coolest OSS community on the web!!
Feeling blessed and ever so humbled to be part of it.
Thank you!!
A Word From Our Sponsors...
To all the good folks below that opted to pay it forward and join our sponsorship program, I salute you!!
Sponsorship cancellations since the last release: 8 ;(
🎉 Feature Release 🎈👯
Breaking Bad!
WARNING! There are breaking change on this drop!
-
NodeShell configuration has moved up in the k9s config file from the context section to the top level config.
More than likely, one uses the same nodeShell image with all the fixins to introspect nodes no matter the cluster. This update DRY's up k9s config and still allows one to opt in/out of nodeShell via the context specific feature gate.
Please see README for the details.NOTE: If you haven't customize the shellPod images on your contexts, the app will move the nodeShell config section to
it's new location and update your clusters information accordingly.
If not, you will need to edit the nodeShell section and manage it from a single location! -
Log view used to default to the last 5mins aka
sinceSeconds: 300.
Changed the default to tail logs instead akasinceSeconds: -1 -
Skins loading changed! In this release, we do away with the context specific skin files. You can now directly specify the skin to use for a given cluster directly in the k9s config file under the cluster configuration. K9s now expects a skins directory in the k9s config home with your skin files. You can use your custom skins and copy them to the
skinsdirectory or use the contributes skins found on this repo root.
Specify the name of the skin in the config file and now your cluster will load the specified skin.
For example: create a skins dir your k9s config home and add one_dark.yml skin file from this repo. Then edit your k9s config file as follows:
k9s:
...
clusters:
fred:
# Override the default skin and use this skin for this cluster.
skin: one_dark # -> Look for a skin file in ~/.config/k9s/skins/one_dark.yml
namespace:
...
view:
active: pod
featureGates:
nodeShell: false
portForwardAddress: localhostThe fred cluster will now load with the specified skin name. Rinse and repeat for other clusters of your liking. In the case where neither the skin dir or skin file are present, k9s will still honor the global skin aka skin.yml in your k9s config home directory to skin all your clusters.
Walk Of SHelm...
Added a Releases view to Helm!
This provides the ability for Helm users to manage their releases directly from k9s.
You can now press enter on a selected Helm install and view all associated releases.
While in the releases view, you can also rollback an install to a previous revision.
Spock! Are You Out Of Your VulScan Mind?
Tired of having malignent folks shoot holes in your prod clusters or failing compliance testing?
Added ability to run image vulnerability scans directly from k9s. You can now monitor your security stance in dev/staging/... clusters
prior to proclaiming It's Open Season... in prod!
As it stands Pod, Deployment, StatefulSet, DaemonSet, CronJob, Job views will feature a new column for Vulnerability Scan aka VS.
NOTE! This feature is gated so you'll need to manually opt in/out by modifying your k9s config file like so:
k9s:
liveViewAutoRefresh: false
enableImageScan: true # <- Yes Please!!
headless: false
...Once enabled, a new column VS (aka Vulnerability Score) should be present on the aforementioned views where you will see your vulnerability scores (Still work in progress!!).
The VS column displays a bit vector aka Sev-1|Sev-2|Sev-3|Sev-4|Sev-5|Sev-Unknown. When the bit is high it indicate the presence of the severity in the scans. Higher order bits = Higher severity
For instance, the following vector 110001 indicates the presence of both critical (Sev-1) and high (Sev-2) and an unclassified severity (aka Sev-Unknown) issues in the scan. Sev-U indicates no classification currently exist in our vulnerability database.
The image scans are run async, rendering the views eventually consistent, hence you may have to give the scores a few cycles for the dust to settle...
Once the caches are primed, subsequent loads should be faster 🤞
You can sort the views by vulnerability score using ShiftV.
Additionally, you can view the full scans report by pressing v on a selected resource.
I've synced my entire Thanksgiving holiday break on this ding dang deal, so hopefully it works for most of you??
Also if you dig this new feature, please make some noise! 😍
💘 This is an experimental feature and likely will require additional TLC 💘
NOTE! The lib we use to scan for vulnerabilities only supports macOS and Linux!!
NOTE: I have yet to test this feature on larger clusters, so likely this may break??
Please take these reports with a grain of salt as likely your mileage will vary and help us
validate the accuracy of the report ie if we cryWolf, is it actually there?
The paint is still fresh on this deal!!
Do You Tube?
My plan is to begin (again!) putting out short k9s episodes with how-tos, tips, tricks and features previews.
Please dial K9s Channel for up coming content...
The first drop should be up by the time you read this!
Resolved Issues
- #2308 Unable to list CRs for crd with only list and get verb without watch verb
- #2301 Add imagePullPolicy and imagePullSecrets on shell_pod for internal registry uses
- #2298 Weird color after plugin usage
- #2297 Select nodes with space does not work anymore
- #2290 Provide release assets for freebsd amd64/arm64
- #2283 Adding auto complete in search bar
- #2219 Add tty: true to the node shell pod manifest
- #2167 Show wrong Configmap data
- #2166 Taint count for the nodes view
- #2165 Restart counter for init containers
- #2162 Make edit work when describing a resource
- #2154 Help and h command does not work if typed into cmdbuff
- #2036 Crashed while do filtering
- #2009 Ctrl-s: Name of file (Describe-....)
- #1513 Problem regarding showing the logs - it hangs/slow on pods which are running for long time
NOTE: Better but not cured! Perf improvements while viewing large cm (7k lines) from 26s->9s - #568 Allow both .yaml and .yml yaml config files
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
v0.28.2
Release v0.28.2
Notes
Thank you to all that contributed with flushing out issues and enhancements for K9s! I'll try to mark some of these issues as fixed. But if you don't mind grab the latest rev and see if we're happier with some of the fixes! If you've filed an issue please help me verify and close. Your support, kindness and awesome suggestions to make K9s better are, as ever, very much noted and appreciated! Also big thanks to all that have allocated their own time to help others on both slack and on this repo!!
As you may know, K9s is not pimped out by corps with deep pockets, thus if you feel K9s is helping your Kubernetes journey, please consider joining our sponsorship program and/or make some noise on social! @kitesurfer
On Slack? Please join us K9slackers
♫ Sounds Behind The Release ♭
A Word From Our Sponsors...
To all the good folks below that opted to pay it forward and join our sponsorship program, I salute you!!
Sponsorship cancellations since the last release:
2;(
Feature Release
Sanitize Me!
Over time, you might end up with a lot of pod cruft on your cluster. Pods that might be completed, erroring out, etc... Once you've completed your pod analysis it could be useful to clear out these pods from your cluster.
In this drop, we introduce a new command sanitize aka z available on pod views otherwise known as The Axe!. This command performs a clean up of all pods that are in either in completed, crashloopBackoff or failed state. This could be especially handy if you run workflows jobs or commands on your cluster that might leave lots of turd pods. Tho this has a phat fail safe dialog please be careful with this one as it is a blunt tool!
Resolved Issues
- Issue #2281 Can't run Node shell
- Issue #2277 bulk actions applied to power filters
- Issue #2273 Error when draining node that is cordoned bug
- Issue #2233 Invalid port-forwarding status displayed over the k9s UI
Contributed PRs
Please be sure to give Big Thanks! and ATTA Girls/Boys! to all the fine contributors for making K9s better for all of us!!
- PR #2280 chore: replace github.com/ghodss/yaml with sigs.k8s.
- PR #2278 README.md: fix typo in netshoot URL
- PR #2275 check if the Node already cordoned when executing Drain
- PR #2247 Delete port forwards when pods get deleted
© 2023 Imhotep Software LLC. All materials licensed under Apache v2.0