kiosk
kiosk copied to clipboard
kubens support
Hi,
kubens allow for fast switching between namespaces by allowing to choose a namespace in a list. The drawback is that current implementation get the list of namespaces from ns resource.
kubens is licensed under Apache 2 and modifying the code to support spaces API is trivial. It could benefit the kiosk community to provide such a tool to the space admin users.
@cortex93 thanks for reporting this issue! Interesting, this would mean we would need to create some sort of kioskctl. However, currently you could do something like:
kubectl get spaces
kubectx my-space
which might be sufficient already. Or is there a problem doing so?
@cortex93 thanks for reporting this issue! Interesting, this would mean we would need to create some sort of kioskctl. However, currently you could do something like:
kubectl get spaces kubectx my-space
which might be sufficient already. Or is there a problem doing so?
kubens support fzf for interactive menu and fuzzy searching. Having one command to list/select spaces would help.
Currently, I have done a quick and dirty hack in kubens, that list spaces when list namespaces fails. I left the binary name kubens
so that we don't have to change our habits, being in a cluster with or without kiosk. I feel it needs a proper home and support.
@cortex93 thanks for clarifying! As I understand it correctly, you want us to implement support for spaces in kubens
? While I agree this would be a nice addition to kubens, I think you should open this issue in the kubens
repository directly, since actual implementation has to be done in that repo and not in the kiosk repository.
If there is anything we can do to help easing this implementation on the kiosk side, let us know.
I doubt kubectx will includes such a specifc things. I was more thinking of loft-sh forking the kubens repo or maintain patched branched or alike.
@cortex93 ah okay I see. In that case I even think we should create some sort of kioskctl
in this repo that basically provides the namespace switching functionality like kubens does, but it would be clearer this belongs to kiosk and we can more easily add kiosk specific features to it later.
However, at the moment I don't think we have the capacity to do that (but when I find some time I'll give it a shot), but if you want to give that a try, I'm very happy to review a pull request.