From ee23f8465f29c05706d92a2a2fa9082c552f08e4 Mon Sep 17 00:00:00 2001 From: derailed Date: Fri, 12 Apr 2019 14:08:47 -0600 Subject: [PATCH] updated release notes --- change_logs/{release_0.4.9.md => release_0.5.0.md} | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) rename change_logs/{release_0.4.9.md => release_0.5.0.md} (64%) diff --git a/change_logs/release_0.4.9.md b/change_logs/release_0.5.0.md similarity index 64% rename from change_logs/release_0.4.9.md rename to change_logs/release_0.5.0.md index 93551cf2..394b16e2 100644 --- a/change_logs/release_0.4.9.md +++ b/change_logs/release_0.5.0.md @@ -1,6 +1,6 @@ -# Release v0.4.9 +# Release v0.5.0 ## Notes @@ -16,6 +16,9 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https ## Change Logs +I am super excited about this drop of K9s. Lot's of cool improvements based on K9s friends excellent feedback! + + ### Popeye Turns out [Popeye](https://github.com/derailed/popeye) is in too much flux at present, thus I've decided to remove it from K9s for the time being. @@ -24,6 +27,15 @@ Turns out [Popeye](https://github.com/derailed/popeye) is in too much flux at pr Added a container view to list all the containers available on a given pod. On a selected pod, you can now press `` to view all of it's associated containers. Once in container view pressing `` on a selected container, will show the container logs. +### Resource Traversals + +> Ever wanted to know where your pods originated from? + +Fear not, K9s has got your back! Some folks have expressed desires to navigate from a deployment to it's pods or see which pods are running on a given node. Whether you are starting from a Node, a Deployment, ReplicaSet, DaemonSet or StatefulSet, you can now simply `` of a selected item a view the associated pods. [Issue #149](https://github.com/derailed/k9s/issues/149) + +### RollingBack ReplicaSets + +You can now select a ReplicaSet and rollback your Deployment to that version. Enter the command mode via `:rs` to view ReplicaSets, select the replica you want to rollback to and use `Ctrl-B` to rollback your deployment to that revision. ---