Fix typos (#3026)
Nathan Baulch
GitHub
parent
9b0ffb87be
commit
420a53317e
|
|
@ -1,6 +1,6 @@
|
|||
# options for analysis running
|
||||
run:
|
||||
# default concurrency is a available CPU number
|
||||
# default concurrency is an available CPU number
|
||||
concurrency: 8
|
||||
|
||||
# timeout for analysis, e.g. 30s, 5m, default is 1m
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ Please refer to our [K9s documentation](https://k9scli.io) site for installation
|
|||
|
||||
Wanna discuss K9s features with your fellow `K9sers` or simply show your support for this tool?
|
||||
|
||||
* Channel: [K9ersSlack](https://k9sers.slack.com/)
|
||||
* Channel: [K9sersSlack](https://k9sers.slack.com/)
|
||||
* Invite: [K9slackers Invite](https://join.slack.com/t/k9sers/shared_invite/enQtOTA5MDEyNzI5MTU0LWQ1ZGI3MzliYzZhZWEyNzYxYzA3NjE0YTk1YmFmNzViZjIyNzhkZGI0MmJjYzhlNjdlMGJhYzE2ZGU1NjkyNTM)
|
||||
|
||||
## Installation
|
||||
|
|
@ -411,13 +411,13 @@ You can now override the context portForward default address configuration by se
|
|||
noIcons: false
|
||||
# Toggles reactive UI. This option provide for watching on disk artifacts changes and update the UI live Defaults to false.
|
||||
reactive: false
|
||||
# By default all contexts wil use the dracula skin unless explicitly overridden in the context config file.
|
||||
# By default all contexts will use the dracula skin unless explicitly overridden in the context config file.
|
||||
skin: dracula # => assumes the file skins/dracula.yaml is present in the $XDG_DATA_HOME/k9s/skins directory
|
||||
# Allows to set certain views default fullscreen mode. (yaml, helm history, describe, value_extender, details, logs) Default false
|
||||
defaultsToFullScreen: false
|
||||
# Toggles icons display as not all terminal support these chars.
|
||||
noIcons: false
|
||||
# Toggles whether k9s should check for the latest revision from the Github repository releases. Default is false.
|
||||
# Toggles whether k9s should check for the latest revision from the GitHub repository releases. Default is false.
|
||||
skipLatestRevCheck: false
|
||||
# When altering kubeconfig or using multiple kube configs, k9s will clean up clusters configurations that are no longer in use. Setting this flag to true will keep k9s from cleaning up inactive cluster configs. Defaults to false.
|
||||
keepMissingClusters: false
|
||||
|
|
@ -944,7 +944,7 @@ k9s:
|
|||
noIcons: false
|
||||
# Toggles reactive UI. This option provide for watching on disk artifacts changes and update the UI live Defaults to false.
|
||||
reactive: false
|
||||
# By default all contexts wil use the dracula skin unless explicitly overridden in the context config file.
|
||||
# By default all contexts will use the dracula skin unless explicitly overridden in the context config file.
|
||||
skin: dracula # => assumes the file skins/dracula.yaml is present in the $XDG_DATA_HOME/k9s/skins directory
|
||||
defaultsToFullScreen: false
|
||||
skipLatestRevCheck: false
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ rev and see if we're happier with some of the fixes!
|
|||
```text
|
||||
>po<ENTER>
|
||||
```
|
||||
+ Similarly to filter on a given resource you can use `/' and type your filter.
|
||||
+ Similarly to filter on a given resource you can use `/` and type your filter.
|
||||
+ In both instances `<ESC>` will back you out of command mode and into navigation mode.
|
||||
|
||||
<br/>
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Most of the refactors are around K8s resource fetching and viewing as well as na
|
|||
|
||||
## Custom Skins Per Cluster
|
||||
|
||||
In this release, we've added support for skins at the cluster level. Do you want K9s to look differently based on which cluster you're connecting to? All you'll need is to name the skin file in the K9s home directory as follows `mycluster_skin.yml`. If no cluster specific skin file is found, the standard `skin.yml` file will be loaded if present. Please checkout the `skins` directory in this repo or PR me if you have cool skins you'd like to share with your fellow K9ers as they will be featured in these release notes and in the project README.
|
||||
In this release, we've added support for skins at the cluster level. Do you want K9s to look differently based on which cluster you're connecting to? All you'll need is to name the skin file in the K9s home directory as follows `mycluster_skin.yml`. If no cluster specific skin file is found, the standard `skin.yml` file will be loaded if present. Please checkout the `skins` directory in this repo or PR me if you have cool skins you'd like to share with your fellow K9sers as they will be featured in these release notes and in the project README.
|
||||
|
||||
## Hot(Ness)?
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
|
|||
|
||||
### Searchable Logs
|
||||
|
||||
There has been quiet a few demands for this feature. It should now be generally available in this drop. It works the same as the resource view ie `/fred`, you can also specify a fuzzy filter using `/-f blee-duh`. The paint is still fresh on that deal and not super confident that it will work nominally as I had to rework the logs to enable. So totally possible I've hosed something in the process.
|
||||
There has been quite a few demands for this feature. It should now be generally available in this drop. It works the same as the resource view ie `/fred`, you can also specify a fuzzy filter using `/-f blee-duh`. The paint is still fresh on that deal and not super confident that it will work nominally as I had to rework the logs to enable. So totally possible I've hosed something in the process.
|
||||
|
||||
### APIServer Dud
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ k9s:
|
|||
|
||||
### K9s Slackers
|
||||
|
||||
I've enabled a [K9s slack channel](https://join.slack.com/t/k9sers/shared_invite/enQtOTAzNTczMDYwNjc5LWJlZjRkNzE2MzgzYWM0MzRiYjZhYTE3NDc1YjNhYmM2NTk2MjUxMWNkZGMzNjJiYzEyZmJiODBmZDYzOGQ5NWM) dedicated to all K9ers. This would be a place for us to meet and discuss ideas and use cases. I'll be honest here I am not a big slack afficionado as I don't do very well with interrupt drive workflows. But I think it would be a great resource for us all.
|
||||
I've enabled a [K9s slack channel](https://join.slack.com/t/k9sers/shared_invite/enQtOTAzNTczMDYwNjc5LWJlZjRkNzE2MzgzYWM0MzRiYjZhYTE3NDc1YjNhYmM2NTk2MjUxMWNkZGMzNjJiYzEyZmJiODBmZDYzOGQ5NWM) dedicated to all K9sers. This would be a place for us to meet and discuss ideas and use cases. I'll be honest here I am not a big slack aficionado as I don't do very well with interrupt drive workflows. But I think it would be a great resource for us all.
|
||||
|
||||
NOTE: Please be kind to each others and threat everyone with respect as I would like this to be a safe and fun place for folks to hangout. Thank you for you support and understanding!!
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Thank you so much for your support!!
|
|||
|
||||
+ [Feature #97](https://github.com/derailed/k9s/issues/97)
|
||||
Changed log view to now use kubectl logs shell command.
|
||||
There was some issues with the previous implementation with missing info and panics.
|
||||
There were some issues with the previous implementation with missing info and panics.
|
||||
NOTE! User must type Ctrl-C to exit the logs and navigate back to K9s
|
||||
+ Reordered containers to show spec.containers first vs spec.initcontainers.
|
||||
+ [Feature #29](https://github.com/derailed/k9s/issues/29)
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Thank you so much for your support!!
|
|||
|
||||
1. [Feature #124](https://github.com/derailed/k9s/issues/124)
|
||||
1. *NodeView* Add current cpu/memory percentages to track current load on nodes.
|
||||
2. *NodeView* Add requested cpu/memory percentages to track how much containers
|
||||
2. *NodeView* Add requested cpu/memory percentages to track how many container
|
||||
resources are requested on the cluster.
|
||||
3. *NodeView* Add requested cpu/memory raw metrics
|
||||
4. *NodeView* Add corresponding column sorters
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Thank you so much for your support and awesome suggestions to make K9s better!!
|
|||
2. The RBAC view will auto-refresh just like any K9s views hence showing live RBAC updates
|
||||
3. RBAC view supports standard K8s verbs ie get,list,deletecollection,watch,create,patch,update,delete.
|
||||
4. Any verbs not in this standard K8s verb list, will end up in the EXTRAS column.
|
||||
5. For non resource URLS, we map standard REST verbs to K8s verbs ie post=create patch=update, etc..
|
||||
5. For non resource URLS, we map standard REST verbs to K8s verbs ie post=create patch=update, etc.
|
||||
6. Added initial sorts by name and group while in RBAC view.
|
||||
7. Usage: To activate, enter command mode via `:cr` or `:ro` for clusterrole(cr)/role(ro), select a row and press `<enter>`
|
||||
8. To bail out of the view and return to previous use `p` or `<esc>`
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Thank you so much for your support and awesome suggestions to make K9s better!!
|
|||
```
|
||||
|
||||
These commands will pull all the available cluster and role bindings associated with these subject types.
|
||||
Use select + `<enter>` to see the associated RBACK policy rules.
|
||||
Use select + `<enter>` to see the associated RBAC policy rules.
|
||||
You can also filter/sort, like in any other K9s views with the added bonus of auto updates when new user/group bindings come into your clusters.
|
||||
|
||||
To see ServiceAccount RBAC policies, you can navigate to the serviceaccount view aka `:sa` and select + `<enter>` to view the associated policy rules.
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ NOTE: In a K9s environment, if you'd like to specify a spinach config file, you
|
|||
|
||||
NOTE: There is a bit more that need to be done on this integration to be complete. Please file an issue if something does not work as expected.
|
||||
|
||||
NOTE: Popeye will run it's own course and K9s is just a viewer for it, so if you'd like additional sanitation or find Popeye related issues, please tune to the corresponding repo!
|
||||
NOTE: Popeye will run its own course and K9s is just a viewer for it, so if you'd like additional sanitation or find Popeye related issues, please tune to the corresponding repo!
|
||||
|
||||
Let us know if you dig it? And share your before/after clusters scores!
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ 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!
|
||||
I am super excited about this drop of K9s. Lots of cool improvements based on K9s friends excellent feedback!
|
||||
|
||||
|
||||
### Popeye
|
||||
|
|
@ -31,7 +31,7 @@ Added a container view to list all the containers available on a given pod. On a
|
|||
|
||||
> 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 `<enter>` of a selected item a view the associated pods. [Issue #149](https://github.com/derailed/k9s/issues/149)
|
||||
Fear not, K9s has got your back! Some folks have expressed desires to navigate from a deployment to its 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 `<enter>` of a selected item a view the associated pods. [Issue #149](https://github.com/derailed/k9s/issues/149)
|
||||
|
||||
### RollingBack ReplicaSets
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
|
|||
|
||||
### Performance... With feelings!
|
||||
|
||||
Ran thru another perf pass and hope I've pushed the needle in the right direction? K9s is now leveraging informers which I think came out of CRDs work. Our initial assessments shows numbers to μsecond updates, down from milliseconds 🎉. Hopefully the outputs are still correct as I have the tendency to make things much faster with incorrect results ;( We hope to hear back from you with a report from your clusters and assessments and brace for good news? This was a deep cycle thru K9s core and more perf will be gain, once we get a chance to vet this new strategy. I'd like to take this opportunity to thank you all for your patience and incredible kindness and support. We certainly hope this drop won't turn out to be a dud as I am fresh out of prozac patches 😩
|
||||
Ran thru another perf pass and hope I've pushed the needle in the right direction? K9s is now leveraging informers which I think came out of CRDs work. Our initial assessments shows numbers to μsecond updates, down from milliseconds 🎉. Hopefully the outputs are still correct as I have the tendency to make things much faster with incorrect results ;( We hope to hear back from you with a report from your clusters and assessments and brace for good news? This was a deep cycle thru K9s core and more perf will be gained, once we get a chance to vet this new strategy. I'd like to take this opportunity to thank you all for your patience and incredible kindness and support. We certainly hope this drop won't turn out to be a dud as I am fresh out of prozac patches 😩
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Provided your K8s services are head(Full), you can now navigate to the pods that
|
|||
|
||||
### Moving Forward!
|
||||
|
||||
In this drop, we've added support for port-forwarding that allows you to exercise your container from your local machine. To setup a port-forward, from the Pod view drill down to a selected Pod's containers, select the container that exposes the port of interest and hit `Ctrl-F`. A dialog will popup allowing you to configure a localhost port to forward to. Once set up, K9s will take you to you to the new PortForward view aka `pf`. Pending your terminal feature and container setup, you should be able to pop the forwarded URL directly into your browse. On iTerm2 me think `command+click` does the trick?
|
||||
In this drop, we've added support for port-forwarding that allows you to exercise your container from your local machine. To setup a port-forward, from the Pod view drill down to a selected Pod's containers, select the container that exposes the port of interest and hit `Ctrl-F`. A dialog will popup allowing you to configure a localhost port to forward to. Once set up, K9s will take you to the new PortForward view aka `pf`. Pending your terminal feature and container setup, you should be able to pop the forwarded URL directly into your browse. On iTerm2 me think `command+click` does the trick?
|
||||
|
||||
Big thanks and ATTABOY! in full effect all week to [Brent](https://github.com/brentco) for filing this initial issue. Please keep in mind, these port-forward babies are a bit expensive to run, so make sure you choose wisely and delete any superfluous PFs!!
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ This feature comes out of [Raman Gupta](https://github.com/rocketraman) report.
|
|||
|
||||
### OldiesButGoodies?
|
||||
|
||||
So the initial few releases of K9s did not have any failsafe counter measures while deleting resources. So we've beefed the deletion logic to make sure you did not inadvertantly blow something away by leveraging
|
||||
So the initial few releases of K9s did not have any failsafe counter measures while deleting resources. So we've beefed the deletion logic to make sure you did not inadvertently blow something away by leveraging
|
||||
dialogs. This was totally a reasonable thing to do! However in case of managed pods, one may want to quickly cycle on or more pod perhaps to pickup a new image or configuration. For this purpose we've introduced an alternate deletion mechanism to delete pod under `alt-k` for kill. Thanks to my fellow frenchma [ftorto](https://github.com/ftorto) for this one ;)
|
||||
|
||||
### HairPlugs!
|
||||
|
|
@ -74,7 +74,7 @@ plugins:
|
|||
scopes:
|
||||
- co
|
||||
description: Sniff
|
||||
# NOTE! Ksniff has been install as a kubectl extension!
|
||||
# NOTE! Ksniff has been installed as a kubectl extension!
|
||||
command: kubectl
|
||||
# Run this command in the background so that I can still do K9s stuff...
|
||||
background: true
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
|
|||
|
||||
Maintenance release.
|
||||
|
||||
In this quick drop, we've opted to nuke any menu shortcut using the infamous `Alt` key. This includes the new pod kill command that is now `Ctrl-K` and for the most part the column sorting shortcuts for CPU% and MEMORY%. My apologizes to all on this fiasco as it turns out I had remapped opt->alt on my local dev machine and space it while trying to offer different key mappings. Will revisit this in the future when things seemer down a bit. Thank you to all that reported on this!
|
||||
In this quick drop, we've opted to nuke any menu shortcut using the infamous `Alt` key. This includes the new pod kill command that is now `Ctrl-K` and for the most part the column sorting shortcuts for CPU% and MEMORY%. My apologizes to all on this fiasco as it turns out I had remapped opt->alt on my local dev machine and space it while trying to offer different key mappings. Will revisit this in the future when things simmer down a bit. Thank you to all that reported on this!
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ alias:
|
|||
|
||||
### Plug For Plugins
|
||||
|
||||
As of this release and based on some users feedback we've moved the plugin section that used to live in the main K9s configuration file out to it's own file. So as of this release we've added a new file in K9s home dir called `plugin.yml`. This is where you will define/share your K9s plugins and define your own commands and menu mnemonics. Here is an example for defining a custom command to show logs.
|
||||
As of this release and based on some users feedback we've moved the plugin section that used to live in the main K9s configuration file out to its own file. So as of this release we've added a new file in K9s home dir called `plugin.yml`. This is where you will define/share your K9s plugins and define your own commands and menu mnemonics. Here is an example for defining a custom command to show logs.
|
||||
|
||||
```yaml
|
||||
# plugin.yml
|
||||
|
|
@ -65,7 +65,7 @@ Special K9s env vars you will have access to are currently for your commands or
|
|||
* GROUPS
|
||||
* COL[0-9+]
|
||||
|
||||
I will setup an plugin/alias repo so we can share these with all K9sers. Please ping me if interested in contributing/sharing your commands. Thank you!!
|
||||
I will setup a plugin/alias repo so we can share these with all K9sers. Please ping me if interested in contributing/sharing your commands. Thank you!!
|
||||
|
||||
### Aye Aye Capt'ain!!
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ You can now use commands like `svc fred` while in command mode to directly navig
|
|||
|
||||
#### Sticky Filters
|
||||
|
||||
You can now keep filters sticky allowing you to filter a view bases on regex, fuzzy or labels and keep the filter live while switching resources. This provides for an horizontal navigation to view the various resources for a given application. Thank you so much [Nobert](https://github.com/ncsibra) for your continuous awesome feedback!!
|
||||
You can now keep filters sticky allowing you to filter a view bases on regex, fuzzy or labels and keep the filter live while switching resources. This provides for a horizontal navigation to view the various resources for a given application. Thank you so much [Nobert](https://github.com/ncsibra) for your continuous awesome feedback!!
|
||||
|
||||
### New Resources
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ Big thanks in full effect to you all, I am so humbled and honored by your kind a
|
|||
|
||||
### Dracula Skin
|
||||
|
||||
Since we're in the thank you phase, might as well lasso in [Josh Symonds](https://github.com/Veraticus) for contributing the `Dracula` K9s skin that is now available in this repo under the skins directory. Here is a sneak peek of what K9s looks like under that skin. I am hopeful that like minded `graphically` inclined K9ers will contribute cool skins for this project for us to share/use in our Kubernetes clusters.
|
||||
Since we're in the thank you phase, might as well lasso in [Josh Symonds](https://github.com/Veraticus) for contributing the `Dracula` K9s skin that is now available in this repo under the skins directory. Here is a sneak peek of what K9s looks like under that skin. I am hopeful that like minded `graphically` inclined K9sers will contribute cool skins for this project for us to share/use in our Kubernetes clusters.
|
||||
|
||||
<img src="https://raw.githubusercontent.com/derailed/k9s/master/assets/skins/dracula.png"/>
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Also I'd like to take this opportunity to recognize and thank a few folks that h
|
|||
|
||||
## Search Enabled For Describe/YAML views
|
||||
|
||||
In this drop we made the Describe/YAML views searchable. So you no longer need to plow thru your resource configurations and get directly to the just of it by using the search command ie `/elvis` + `enter`. You can use the familiar keys `n` and `N` to nav back and forth to the next occurrence in a circular buffer fashion once you've reached the BOF/EOF. It's the little things in life...
|
||||
In this drop we made the Describe/YAML views searchable. So you no longer need to plow thru your resource configurations and get directly to the gist of it by using the search command ie `/elvis` + `enter`. You can use the familiar keys `n` and `N` to nav back and forth to the next occurrence in a circular buffer fashion once you've reached the BOF/EOF. It's the little things in life...
|
||||
|
||||
## And On Another Note...
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ NOTE: Pulses are very much experimental and could totally bomb on your clusters!
|
|||
|
||||
## BReaking Bad!
|
||||
|
||||
In this drop I've broken a few things (that I know off...), here is the list as I can recall...
|
||||
In this drop I've broken a few things (that I know of...), here is the list as I can recall...
|
||||
|
||||
1. Toggle header aka `my red headed step child`. Key moved (again!) now `Ctrl-e`
|
||||
2. Skin yaml layout CHANGED! Moved table and xray sections under views and added charts section.
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ As you might have heard, the good Kubernetes folks just dropped some big feature
|
|||
<img src="https://raw.githubusercontent.com/derailed/k9s/master/assets/k9s_popeye.png" align="center" width="400" height="auto"/>
|
||||
|
||||
As you may know, I am the author of [Popeye](https://popeyecli.io) a Kubernetes cluster linter/sanitizer. Popeye scans your clusters live and reports potential issues, things like: referential integrity, misconfiguration, resource usage, etc...
|
||||
In this drop, we've integrated K9s and Popeye to produce what I believe is a killer combo. Not only can you manage/observe your cluster resources in the wild, but you can now assert that your resources are indeed cool and potentially get ride of dead weights that might add up to your monthly cloud service bills. How cool is that?
|
||||
In this drop, we've integrated K9s and Popeye to produce what I believe is a killer combo. Not only can you manage/observe your cluster resources in the wild, but you can now assert that your resources are indeed cool and potentially get rid of dead weights that might add up to your monthly cloud service bills. How cool is that?
|
||||
|
||||
In order to run your sanitization and produce reports, you can enter a new command `:popeye`. Once your cluster sanitization is complete, you can use familiar keyboard shortcuts to sort columns and view the sanitization reports by pressing `enter` on a given resource linter. Popeye also supports a configuration file namely `spinach.yml`, this file provides for customizing what resources get scanned as well as setting different severity levels to your own company policies. Please read the Popeye docs on how to customize your reports. The spinach.yml file will be read from K9s home directory `$HOME/.k9s/MY_CLUSTER_CONTEXT_NAME_spinach.yml`
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ NOTE! This is very much still experimental, so you may experience some disturban
|
|||
|
||||
## Command History Support
|
||||
|
||||
K9s now supports for command history. Entering command mode via `:` you can now up/down arrow to navigate thru your command history. Pression `tab` or `ctrl-e` or `->` will activate the selected command upon `enter`.
|
||||
K9s now supports for command history. Entering command mode via `:` you can now up/down arrow to navigate thru your command history. Pressing `tab` or `ctrl-e` or `->` will activate the selected command upon `enter`.
|
||||
|
||||
## K9s Icons
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ As always please help me flush/report issues and I'll address them promptly! Tha
|
|||
|
||||
## Improved Node Shell Usability
|
||||
|
||||
In this drop we've changed the configuration of the node shell action that let's you shell into nodes. Big thanks to [Patrick Decat](https://github.com/pdecat) for helping us flesh out this beta feature! We've added configuration to not only customize the image but also the resources and namespace on how to run these K9s pods on your clusters. The new configuration is set at the cluster scope level.
|
||||
In this drop we've changed the configuration of the node shell action that lets you shell into nodes. Big thanks to [Patrick Decat](https://github.com/pdecat) for helping us flesh out this beta feature! We've added configuration to not only customize the image but also the resources and namespace on how to run these K9s pods on your clusters. The new configuration is set at the cluster scope level.
|
||||
|
||||
Here is an example of the new pod shell config options:
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_inv
|
|||
|
||||
## Resolved Issues
|
||||
|
||||
* [Issue #1123](https://github.com/derailed/k9s/issues/1123) Cannotresponse to keyboard strike after exit pod shell in windows 10
|
||||
* [Issue #1123](https://github.com/derailed/k9s/issues/1123) Cannot respond to keyboard strike after exit pod shell in windows 10
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Azar](https://github.com/azarudeena)
|
||||
* [Tim Orling](https://github.com/moto-timo)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering you Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Thank you!!
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Thomas Peter Bernsten](https://github.com/tpberntsen)
|
||||
* [EMR-Bear](https://github.com/emrbear)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Thank you!!
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ Thank you!!
|
|||
|
||||
## !!BREAKING CHANGE!!... We've moved!
|
||||
|
||||
As of this drop, k9s home directory is now configurable via [XDG](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html). Please see the specification depending on your platform of choice. You will now need to set or use the default for `$XDG_CONFIG_HOME` if not already present on your system. This is now the defacto replacement for`HOME/.k9s` as K9s will no longer honor this directory to load artifacts such as config, skins, views, etc... If you have existing customizations, you will need to move those over to your `$XDG_CONFIG_HOME/k9s` dir.
|
||||
As of this drop, k9s home directory is now configurable via [XDG](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html). Please see the specification depending on your platform of choice. You will now need to set or use the default for `$XDG_CONFIG_HOME` if not already present on your system. This is now the de facto replacement for`HOME/.k9s` as K9s will no longer honor this directory to load artifacts such as config, skins, views, etc... If you have existing customizations, you will need to move those over to your `$XDG_CONFIG_HOME/k9s` dir.
|
||||
|
||||
This feature is still fresh and we could have totally missed a piece, so please proceed with caution and keep that issue tracker handy...
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_inv
|
|||
## A Word From Our Sponsors!
|
||||
|
||||
I would like to extend a `Big Thank You` to the following generous K9s friends for joining our sponsorship program and supporting this project!
|
||||
Without your support this project will be another cadaver in Github's infamous `Dead Program Society`. Thank you!!
|
||||
Without your support this project will be another cadaver in GitHub's infamous `Dead Program Society`. Thank you!!
|
||||
|
||||
* 😻 [Antoine Meaussone](https://github.com/Ameausoone)
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ If you would like to support us, you can either join our github sponsors or purc
|
|||
|
||||
## Resolved Issues
|
||||
|
||||
* [Issue #1063](https://github.com/derailed/k9s/issues/1063) Wierd colors on windows (Don't do windows so please help verify!)
|
||||
* [Issue #1063](https://github.com/derailed/k9s/issues/1063) Weird colors on windows (Don't do windows so please help verify!)
|
||||
* [Issue #1061](https://github.com/derailed/k9s/issues/1061) Container shell Windows (Don't do windows so please help verify!)
|
||||
* [Issue #1059](https://github.com/derailed/k9s/issues/1059) Monokai skin broken\
|
||||
* [Issue #177](https://github.com/derailed/k9s/issues/177) Shell first character lost
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
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!
|
||||
|
||||
If you feel K9s is helping your Kubernetes journey, please consider joining our [sponsorhip program](https://github.com/sponsors/derailed) and/or make some noise on social! [@kitesurfer](https://twitter.com/kitesurfer)
|
||||
If you feel K9s is helping your Kubernetes journey, please consider joining our [sponsorship program](https://github.com/sponsors/derailed) and/or make some noise on social! [@kitesurfer](https://twitter.com/kitesurfer)
|
||||
|
||||
On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_invite/enQtOTA5MDEyNzI5MTU0LWQ1ZGI3MzliYzZhZWEyNzYxYzA3NjE0YTk1YmFmNzViZjIyNzhkZGI0MmJjYzhlNjdlMGJhYzE2ZGU1NjkyNTM)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
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!
|
||||
|
||||
If you feel K9s is helping your Kubernetes journey, please consider joining our [sponsorhip program](https://github.com/sponsors/derailed) and/or make some noise on social! [@kitesurfer](https://twitter.com/kitesurfer)
|
||||
If you feel K9s is helping your Kubernetes journey, please consider joining our [sponsorship program](https://github.com/sponsors/derailed) and/or make some noise on social! [@kitesurfer](https://twitter.com/kitesurfer)
|
||||
|
||||
On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_invite/enQtOTA5MDEyNzI5MTU0LWQ1ZGI3MzliYzZhZWEyNzYxYzA3NjE0YTk1YmFmNzViZjIyNzhkZGI0MmJjYzhlNjdlMGJhYzE2ZGU1NjkyNTM)
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Andrew Aadland](https://github.com/DaemonDude23)
|
||||
* [Michael Albers](https://github.com/michaeljohnalbers)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
|
|||
|
|
@ -20,8 +20,8 @@ May need a few rapid fires to regain some sanity so please bare with us and than
|
|||
## Resolved Issues
|
||||
|
||||
* [Issue #1308](https://github.com/derailed/k9s/issues/1308) Command auto-complete suggestions disappear after screen refresh interval #1308
|
||||
* [Issue #1307](https://github.com/derailed/k9s/issues/1307) Displayed Cluster name is always read from current-contex
|
||||
* [Issue #1296](https://github.com/derailed/k9s/issues/1244) Scoobie doo was not a cow - NOTE: Switch to dialog to keep live context!
|
||||
* [Issue #1307](https://github.com/derailed/k9s/issues/1307) Displayed Cluster name is always read from current-context
|
||||
* [Issue #1296](https://github.com/derailed/k9s/issues/1244) Scoobie-Doo was not a cow - NOTE: Switch to dialog to keep live context!
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Maxim](https://github.com/bsod90)
|
||||
* [Sönke Schau](https://github.com/xgcssch)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ Doh! Sorry ;( with feelings...
|
|||
* [Issue #1361](https://github.com/derailed/k9s/issues/1361) Pulses not displaying graphs
|
||||
* [Issue #1358](https://github.com/derailed/k9s/issues/1358) Namespace list is empty
|
||||
* [Issue #1357](https://github.com/derailed/k9s/issues/1357) Benchmarks doesn't work on windows
|
||||
* [Issue #1355](https://github.com/derailed/k9s/issues/1355) Trace log level does not exists
|
||||
* [Issue #1355](https://github.com/derailed/k9s/issues/1355) Trace log level does not exist
|
||||
* [Issue #1345](https://github.com/derailed/k9s/issues/1345) Access denied after context switch
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Maxim](https://github.com/bsod90)
|
||||
* [Sönke Schau](https://github.com/xgcssch)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Maxim](https://github.com/bsod90)
|
||||
* [Sönke Schau](https://github.com/xgcssch)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [uderik](https://github.com/uderik)
|
||||
* [Daimler](https://github.com/Daimler) wOOt!! Mercedes Benz sponsorship! How cool is that?
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Timothy C. Arland](https://github.com/tcarland)
|
||||
* [Julie Ng](https://github.com/julie-ng)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_inv
|
|||
## Resolved Issues
|
||||
|
||||
* [Issue #1402](https://github.com/derailed/k9s/issues/1402) Sort functionality does not work properly on v0.25.16
|
||||
* [Issue #1401](https://github.com/derailed/k9s/issues/1401) Nothin selected when last item deleted
|
||||
* [Issue #1401](https://github.com/derailed/k9s/issues/1401) Nothing selected when last item deleted
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ I want to recognize the following folks that have been kind enough to join our s
|
|||
* [Maxim](https://github.com/bsod90)
|
||||
* [Sönke Schau](https://github.com/xgcssch)
|
||||
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our k9ers community at large.
|
||||
So if you feel K9s is helping with your productivity while administering your Kubernetes clusters, please consider pitching in as it will go a long way in ensuring a thriving environment for this repo and our K9sers community at large.
|
||||
|
||||
Also please take some time and give a huge shoot out to all the good folks below that have spent time plowing thru the code to help improve K9s for all of us!
|
||||
|
||||
|
|
@ -36,7 +36,7 @@ Thank you!!
|
|||
* [Issue #1361](https://github.com/derailed/k9s/issues/1361) Pulses not displaying graphs
|
||||
* [Issue #1358](https://github.com/derailed/k9s/issues/1358) Namespace list is empty
|
||||
* [Issue #1357](https://github.com/derailed/k9s/issues/1357) Benchmarks doesn't work on windows
|
||||
* [Issue #1355](https://github.com/derailed/k9s/issues/1355) Trace log level does not exists
|
||||
* [Issue #1355](https://github.com/derailed/k9s/issues/1355) Trace log level does not exist
|
||||
* [Issue #1345](https://github.com/derailed/k9s/issues/1345) Access denied after context switch
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ On Slack? Please join us [K9slackers](https://join.slack.com/t/k9sers/shared_inv
|
|||
|
||||
## Maintenance Release
|
||||
|
||||
Please join me in giving a big THANK YOU and ATTA BOY!! to [Aleksei Romanenko](https://github.com/slimus) for allocating his personal time in helping out his fellow K9ser's with issues, PRs and slack!!
|
||||
Please join me in giving a big THANK YOU and ATTA BOY!! to [Aleksei Romanenko](https://github.com/slimus) for allocating his personal time in helping out his fellow K9sers with issues, PRs and slack!!
|
||||
|
||||
Also in the last drop, I'd updated k8s API's to the latest which caused some `disturbance in the farce!` and hosed AWS cluster connections in the same swop ;( Please see [Issue#119](https://github.com/derailed/k9s/issues/1619) for `a` resolve... I did not catch it early enough hence the release bump on this drop. My bad!!
|
||||
|
||||
|
|
@ -32,7 +32,7 @@ Also in the last drop, I'd updated k8s API's to the latest which caused some `di
|
|||
|
||||
* [Issue #1655](https://github.com/derailed/k9s/issues/1655) Text not appearing in context windows
|
||||
* [Issue #1654](https://github.com/derailed/k9s/issues/1654) K9s crash on m1 with index out of range [0] with length 0
|
||||
* [Issue #1652](https://github.com/derailed/k9s/issues/1652) HPA with custom metrics has "Target% column showing "unknown/unknown"
|
||||
* [Issue #1652](https://github.com/derailed/k9s/issues/1652) HPA with custom metrics has "Target%" column showing "unknown/unknown"
|
||||
* [Issue #1639](https://github.com/derailed/k9s/issues/1639) Helm releases view broken after interacting with 0.25.21
|
||||
|
||||
## Resolved PR
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Please give `Big Thanks!` and `ATTA Girls/Boys!` to all the fine contributors fo
|
|||
|
||||
* [PR #1910](https://github.com/derailed/k9s/pull/1910) Replace x86_64 to amd64 build
|
||||
* [PR #1877](https://github.com/derailed/k9s/pull/1877) Bug: portforward custom containers not showing
|
||||
* [PR #1874](https://github.com/derailed/k9s/pull/1874) Feat: Add noLastestRevCheck config option
|
||||
* [PR #1874](https://github.com/derailed/k9s/pull/1874) Feat: Add noLatestRevCheck config option
|
||||
* [PR #1872](https://github.com/derailed/k9s/pull/1872) Docs: Add k8s client compatibility matrix
|
||||
* [PR #1871](https://github.com/derailed/k9s/pull/1871) Bug: update scanSA calls to account for blank service accounts
|
||||
* [PR #1866](https://github.com/derailed/k9s/pull/1866) Bug: Fix order of arguments for CanI function call
|
||||
|
|
|
|||
|
|
@ -119,7 +119,7 @@ While in the releases view, you can also rollback an install to a previous revis
|
|||
|
||||
### Spock! Are You Out Of Your VulScan Mind?
|
||||
|
||||
Tired of having malignent folks shoot holes in your prod clusters or failing compliance testing?
|
||||
Tired of having malignant 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!
|
||||
|
|
|
|||
|
|
@ -85,13 +85,13 @@ There was a few issues with the way K9s persists it's configuration and various
|
|||
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"!!
|
||||
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 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:
|
||||
|
||||
```yaml
|
||||
# $XDG_CONFIG_HOME/k9s/config.yaml
|
||||
# File will be autogenerated will all the default fixins if not found in the config specification.
|
||||
# File will be autogenerated with all the default fixins if not found in the config specification.
|
||||
k9s:
|
||||
liveViewAutoRefresh: false
|
||||
refreshRate: 2
|
||||
|
|
@ -215,7 +215,7 @@ I feel this is an improvement (tho I might be unanimous on this!) especially for
|
|||
|
||||
# Got Prompt?
|
||||
|
||||
In this drop, we've also gave the k9s command prompt aka `:xxx` some love.
|
||||
In this drop, we've also given 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.
|
||||
|
|
@ -230,16 +230,16 @@ Put these frequent flyers command in an alias and now you can nav your clusters
|
|||
|
||||
# All Is Love?
|
||||
|
||||
🎵 `On The twentieth day of Christmas my true love gave to me... Ten worklords a-leaping??...` 🎵
|
||||
🎵 `On The twentieth day of Christmas my true love gave to me... Ten workloads 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.
|
||||
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 `kubectl 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.
|
||||
|
||||
---
|
||||
|
||||
# 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 ;(
|
||||
The `Vulscan` feature did not get out unscathed ;(
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ 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 ;(
|
||||
The `Vulscan` feature did not get out unscathed ;(
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ Please dial [K9s Channel](https://www.youtube.com/channel/UC897uwPygni4QIjkPCpgj
|
|||
## Resolved Issues
|
||||
|
||||
* [#2394](https://github.com/derailed/k9s/issues/2394) Allow setting custom log dir
|
||||
* [#2393](https://github.com/derailed/k9s/issues/2393) When switching contexts k9s does not switching to cluster's pod/namespaces/other k8s kinds view
|
||||
* [#2393](https://github.com/derailed/k9s/issues/2393) When switching contexts k9s does not switch to cluster's pod/namespaces/other k8s kinds view
|
||||
* [#2387](https://github.com/derailed/k9s/issues/2387) Invalid namespace xxx - with feelings!
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ Please dial [K9s Channel](https://www.youtube.com/channel/UC897uwPygni4QIjkPCpgj
|
|||
|
||||
## Resolved Issues
|
||||
|
||||
* [#2434](https://github.com/derailed/k9s/issues/2434) readOnly: true in config.yaml doesnt get overriden by readOnly: false in cluster config
|
||||
* [#2434](https://github.com/derailed/k9s/issues/2434) readOnly: true in config.yaml doesn't get overridden by readOnly: false in cluster config
|
||||
* [#2430](https://github.com/derailed/k9s/issues/2430) Referencing a namespace with the name of an alias inside an alias causes infinite loop
|
||||
* [#2428](https://github.com/derailed/k9s/issues/2428) Boom!! runtime error: invalid memory address or nil pointer dereference - v0.30.8
|
||||
* [#2421](https://github.com/derailed/k9s/issues/2421) k9s/config.yaml configuration file is overwritten on launch
|
||||
|
|
|
|||
|
|
@ -137,7 +137,7 @@ Please dial [K9s Channel](https://www.youtube.com/channel/UC897uwPygni4QIjkPCpgj
|
|||
|
||||
## Resolved Issues
|
||||
|
||||
* [#2434](https://github.com/derailed/k9s/issues/2434) readOnly: true in config.yaml doesnt get overriden by readOnly: false in cluster config
|
||||
* [#2434](https://github.com/derailed/k9s/issues/2434) readOnly: true in config.yaml doesn't get overridden by readOnly: false in cluster config
|
||||
* [#2430](https://github.com/derailed/k9s/issues/2430) Referencing a namespace with the name of an alias inside an alias causes infinite loop
|
||||
* [#2428](https://github.com/derailed/k9s/issues/2428) Boom!! runtime error: invalid memory address or nil pointer dereference - v0.30.8
|
||||
* [#2421](https://github.com/derailed/k9s/issues/2421) k9s/config.yaml configuration file is overwritten on launch
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ Please dial [K9s Channel](https://www.youtube.com/channel/UC897uwPygni4QIjkPCpgj
|
|||
|
||||
## Resolved Issues
|
||||
|
||||
* [#2476](https://github.com/derailed/k9s/issues/2476) Pod's are not displayed for the selected namespace. Hopefully!
|
||||
* [#2476](https://github.com/derailed/k9s/issues/2476) Pods are not displayed for the selected namespace. Hopefully!
|
||||
* [#2471](https://github.com/derailed/k9s/issues/2471) Shell autocomplete functions do not work correctly
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -166,7 +166,7 @@ func (c *Config) CurrentContext() (*api.Context, error) {
|
|||
return c.GetContext(n)
|
||||
}
|
||||
|
||||
// GetContext fetch a given context or error if it does not exists.
|
||||
// GetContext fetch a given context or error if it does not exist.
|
||||
func (c *Config) GetContext(n string) (*api.Context, error) {
|
||||
cfg, err := c.RawConfig()
|
||||
if err != nil {
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ const (
|
|||
// DefaultFileMod default unix perms for k9s files.
|
||||
DefaultFileMod os.FileMode = 0600
|
||||
|
||||
// MainConfigFile track main configuration file..
|
||||
// MainConfigFile track main configuration file.
|
||||
MainConfigFile = "config.yaml"
|
||||
)
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ func NewImageScans() ImageScans {
|
|||
}
|
||||
}
|
||||
|
||||
// ShouldExclude checks if scan should be excluder given ns/labels
|
||||
// ShouldExclude checks if scan should be excluded given ns/labels
|
||||
func (i ImageScans) ShouldExclude(ns string, ll map[string]string) bool {
|
||||
if !i.Enable {
|
||||
return false
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ func validateRange(v int) bool {
|
|||
return true
|
||||
}
|
||||
|
||||
// Threshold tracks threshold to alert user when excided.
|
||||
// Threshold tracks threshold to alert user when exceeded.
|
||||
type Threshold map[string]*Severity
|
||||
|
||||
// NewThreshold returns a new threshold.
|
||||
|
|
@ -90,7 +90,7 @@ func (t Threshold) LevelFor(k string, v int) SeverityLevel {
|
|||
return SeverityLow
|
||||
}
|
||||
|
||||
// SeverityColor returns an defcon level associated level.
|
||||
// SeverityColor returns a defcon level associated level.
|
||||
func (t *Threshold) SeverityColor(k string, v int) string {
|
||||
// nolint:exhaustive
|
||||
switch t.LevelFor(k, v) {
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ const (
|
|||
FlashErr
|
||||
)
|
||||
|
||||
// LevelMessage tracks an message and severity.
|
||||
// LevelMessage tracks a message and severity.
|
||||
type LevelMessage struct {
|
||||
Level FlashLevel
|
||||
Text string
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ type LogsListener interface {
|
|||
// LogStop indicates logging was canceled.
|
||||
LogStop()
|
||||
|
||||
// LogResume indicates loggings has resumed.
|
||||
// LogResume indicates logging has resumed.
|
||||
LogResume()
|
||||
|
||||
// LogCanceled indicates no more logs will come.
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ func TestFieldClone(t *testing.T) {
|
|||
assert.NotEqual(t, fmt.Sprintf("%p", f), fmt.Sprintf("%p", f1))
|
||||
}
|
||||
|
||||
func TestRowlabelize(t *testing.T) {
|
||||
func TestRowLabelize(t *testing.T) {
|
||||
uu := map[string]struct {
|
||||
row model1.Row
|
||||
cols []int
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ import (
|
|||
"k8s.io/apimachinery/pkg/runtime/schema"
|
||||
)
|
||||
|
||||
// Alias renders a aliases to screen.
|
||||
// Alias renders an aliases to screen.
|
||||
type Alias struct {
|
||||
Base
|
||||
}
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ func (c Chart) diagnose(s string) error {
|
|||
// ----------------------------------------------------------------------------
|
||||
// Helpers...
|
||||
|
||||
// ReleaseRes represents an helm chart resource.
|
||||
// ReleaseRes represents a helm chart resource.
|
||||
type ReleaseRes struct {
|
||||
Release *release.Release
|
||||
}
|
||||
|
|
|
|||
|
|
@ -280,7 +280,7 @@ func (a *App) Flash() *model.Flash {
|
|||
// ----------------------------------------------------------------------------
|
||||
// Helpers...
|
||||
|
||||
// AsKey converts rune to keyboard key.,.
|
||||
// AsKey converts rune to keyboard key.
|
||||
func AsKey(evt *tcell.EventKey) tcell.Key {
|
||||
if evt.Key() != tcell.KeyRune {
|
||||
return evt.Key()
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ func NewPrompt(app *App, noIcons bool, styles *config.Styles) *Prompt {
|
|||
return &p
|
||||
}
|
||||
|
||||
// SendKey sends an keyboard event (testing only!).
|
||||
// SendKey sends a keyboard event (testing only!).
|
||||
func (p *Prompt) SendKey(evt *tcell.EventKey) {
|
||||
p.keyboard(evt)
|
||||
}
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ func (c *Interpreter) Reset(s string) *Interpreter {
|
|||
return c
|
||||
}
|
||||
|
||||
// GetLine teturns the prompt.
|
||||
// GetLine returns the prompt.
|
||||
func (c *Interpreter) GetLine() string {
|
||||
return strings.TrimSpace(c.line)
|
||||
}
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ func (v *LiveView) InCmdMode() bool {
|
|||
return v.cmdBuff.InCmdMode()
|
||||
}
|
||||
|
||||
// ResourceFailed notifies when their is an issue.
|
||||
// ResourceFailed notifies when there is an issue.
|
||||
func (v *LiveView) ResourceFailed(err error) {
|
||||
v.text.SetTextAlign(tview.AlignCenter)
|
||||
x, _, w, _ := v.GetRect()
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@ func (p *Pod) shellCmd(evt *tcell.EventKey) *tcell.EventKey {
|
|||
return nil
|
||||
}
|
||||
|
||||
if err := containerShellin(p.App(), p, path, ""); err != nil {
|
||||
if err := containerShellIn(p.App(), p, path, ""); err != nil {
|
||||
p.App().Flash().Err(err)
|
||||
}
|
||||
|
||||
|
|
@ -358,7 +358,7 @@ func (p *Pod) transferCmd(evt *tcell.EventKey) *tcell.EventKey {
|
|||
// ----------------------------------------------------------------------------
|
||||
// Helpers...
|
||||
|
||||
func containerShellin(a *App, comp model.Component, path, co string) error {
|
||||
func containerShellIn(a *App, comp model.Component, path, co string) error {
|
||||
if co != "" {
|
||||
resumeShellIn(a, comp, path, co)
|
||||
return nil
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ func (t *Table) HeaderIndex(colName string) (int, bool) {
|
|||
return 0, false
|
||||
}
|
||||
|
||||
// SendKey sends an keyboard event (testing only!).
|
||||
// SendKey sends a keyboard event (testing only!).
|
||||
func (t *Table) SendKey(evt *tcell.EventKey) {
|
||||
t.app.Prompt().SendKey(evt)
|
||||
}
|
||||
|
|
|
|||
|
|
@ -312,7 +312,7 @@ func (x *Xray) shellCmd(evt *tcell.EventKey) *tcell.EventKey {
|
|||
path = *spec.ParentPath()
|
||||
}
|
||||
|
||||
if err := containerShellin(x.app, x, path, co); err != nil {
|
||||
if err := containerShellIn(x.app, x, path, co); err != nil {
|
||||
x.app.Flash().Err(err)
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
K9s plugins extend the tool to provide additional functionality via actions to further help you observe or administer your Kubernetes clusters.
|
||||
|
||||
Following is an example of some of plugin files in this directory. Other files are not listed in this table.
|
||||
Following is an example of some plugin files in this directory. Other files are not listed in this table.
|
||||
|
||||
| Plugin-Name | Description | Available on Views | Shortcut | Kubectl plugin, external dependencies |
|
||||
| ------------------------------ | ---------------------------------------------------------------------------- | ----------------------------------- |-----------| ------------------------------------------------------------------------------------- |
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
# Manage cert-manager Certificate resouces via cmctl.
|
||||
# Manage cert-manager Certificate resources via cmctl.
|
||||
# See: https://github.com/cert-manager/cmctl
|
||||
plugins:
|
||||
cert-status:
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ plugins:
|
|||
shortCut: Shift-L
|
||||
description: "loki fmt"
|
||||
scopes:
|
||||
- cantainers
|
||||
- containers
|
||||
command: logcli
|
||||
background: false
|
||||
args:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
# Before deleting an object you need to ensure that all finalizers has been removed. Usually this would be done
|
||||
# by the specific controller but under some circumstances it is possible to encounter a set of objects blocked
|
||||
# for deletion.
|
||||
# This plugins makes this task easier by providing a shortcut to directly removing them all.
|
||||
# This plugin makes this task easier by providing a shortcut to directly removing them all.
|
||||
# Be careful when using this plugin as it may leave dangling resources or instantly deleting resources that were
|
||||
# blocked by the finalizers.
|
||||
# Author: github.com/jalvarezit
|
||||
|
|
|
|||
Loading…
Reference in New Issue