Context configs: context directory created under wrong cluster after context switch #3162
Labels
Comments
rocketraman
changed the title
|
@rocketraman Weird?? I can't seem to repro this. The config seems to be written correctly to the right cluster/context after the ctx switch. Perhaps including the logs will shine some insight... |
|
I have also experienced this. |
|
I added some additional debug |
|
@derailed Here are the logs (not including the additional debug added by @uozalp ): The reproduction was slightly different than I stated in my OP:
The end result of the The diffs between the two are almost the same except the cluster identifier: |
|
Here are the logs with the debug commit from @uozalp: |
|
@uozalp @rocketraman Thank you both for the additional details! |
derailed
added
bug
Merged
|
Fixed v0.40.6 |
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this issue
Mar 10, 2025
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [derailed/k9s](https://github.com/derailed/k9s) | patch | `v0.40.5` -> `v0.40.6` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>derailed/k9s (derailed/k9s)</summary> ### [`v0.40.6`](https://github.com/derailed/k9s/releases/tag/v0.40.6) [Compare Source](derailed/k9s@v0.40.5...v0.40.6) <img src="https://raw.githubusercontent.com/derailed/k9s/master/assets/k9s.png" align="center" width="800" height="auto"/> ### Release v0.40.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](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) #### Maintenance Release! ##### Breaking change Moved `portForwardAddress` out of clusterXXX/contextYYY/config.yaml and into the main K9s config file. This is a global preference based on your setup vs a cluster/context specific attribute. K9s will nag you in the logs if a specific context config still contains this attribute but should not prevent the configuration load. ##### Column Blow Reloaded! We've added another property to the custom view. You can now also specify namespace specific column definition for a given resource. For instance, view pods in any namespace using one configuration and view pods in `fred` namespace using an alternate configuration. ```yaml ### views.yaml views: ### Using this for all pods... v1/pods: columns: - AGE - NAMESPACE|WR # => 🌚 Specifies the NAMESPACE column to be right aligned and only visible while in wide mode - ZORG:.metadata.labels.fred\.io\.kubernetes\.blee # => 🌚 extract fred.io.kubernetes.blee label into it's own column - BLEE:.metadata.annotations.blee|R # => 🌚 extract annotation blee into it's own column and right align it - NAME - IP - NODE - STATUS - READY - MEM/RL|S # => 🌚 Overrides std resource default wide attribute via `S` for `Show` - '%MEM/R|' # => NOTE! column names with non alpha names need to be quoted as columns must be strings! ### Use this instead for pods in namespace `fred` v1/pods@fred: # => 🌚 New v0.40.6! Customize columns for a given resource and namespace! columns: - AGE - NAMESPACE|WR ``` Additionally, we've added a new column attribute aka `Show` -> `S`. This allows you to now override the default resource column `wide` attribute when set. *** #### Videos Are In The Can! Please dial [K9s Channel](https://www.youtube.com/channel/UC897uwPygni4QIjkPCpgjmw) for up coming content... - [K9s v0.40.0 -Column Blow- Sneak peek](https://youtu.be/iy6RDozAM4A) - [K9s v0.31.0 Configs+Sneak peek](https://youtu.be/X3444KfjguE) - [K9s v0.30.0 Sneak peek](https://youtu.be/mVBc1XneRJ4) - [Vulnerability Scans](https://youtu.be/ULkl0MsaidU) *** #### Resolved Issues - [#​3179](derailed/k9s#3179) Resource name with full api or group displayed (somewhere and sometimes) - [#​3178](derailed/k9s#3178) Cronjobs with the same name in different namespaces appear together - [#​3176](derailed/k9s#3176) Trigger all marked cronjobs - [#​3162](derailed/k9s#3162) Context configs: context directory created under wrong cluster after context switch - [#​3161](derailed/k9s#3161) Force wide-only columns to appear outside of wide view - [#​3147](derailed/k9s#3147) Prompt style is overriden by body - [#​3139](derailed/k9s#3139) CPU/R:L and MEM/R:L columns invalid in views.yaml - [#​3138](derailed/k9s#3138) Subresources are not shown correctly in the RBAC view *** #### Contributed MRs Please be sure to give `Big Thanks!` and `ATTA Girls/Boys!` to all the fine contributors for making K9s better for all of us!! - [#​3182](derailed/k9s#3182) fix: Use the latest version when downloading the Ubuntu deb file - [#​3168](derailed/k9s#3168) fix(history): handle cases where special commands add their command their command to the history - [#​3159](derailed/k9s#3159) Added hard contrast gruvbox skins - [#​3149](derailed/k9s#3149) fix: Pass grv on gotoResource as a String to fix non-default apiGroup list - [#​3149](derailed/k9s#3149) Add externalsecrets plugin - [#​3140](derailed/k9s#3140) fix: Avoid false positive matches in enableRegion ([#​3093](derailed/k9s#3093)) <img src="https://raw.githubusercontent.com/derailed/k9s/master/assets/imhotep_logo.png" width="32" height="auto"/> © 2025 Imhotep Software LLC. All materials licensed under [Apache v2.0](http://www.apache.org/licenses/LICENSE-2.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xOTAuMSIsInVwZGF0ZWRJblZlciI6IjM5LjE5MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Say we have 2 contexts, context-1 and context-2. Each of these points to a different cluster, cluster-1 and cluster-2 respectively.
If we now start k9s with
context-1active, at the top-left k9s shows:As expected, a context-specific configuration is created in the "Context Configs" with the following directory name:
Now, in k9s use the
ctxswitcher to switch tocontext-2. Now, k9s shows at the top-left the expected values:However, a context-specific configuration is created in the "Context Configs" with the following unexpected directory, where the cluster matches the initial cluster k9s was started with:
The content of that directory appears to be a copy of
clusters/cluster-2/context-2/(assuming it already existed previously).Expected behavior
I would expect each cluster-n directory to only include the relevant context-n directory.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: