Default contexts and /.kube subfolders?

Hi,

By default my config files generated by magnum/openstack for kubernetes are in a config file I export these with:

for CLUSTER in $(openstack coe cluster list -c name -f value); do
 mkdir -p ~/.kube/${CLUSTER}
 openstack coe cluster config ${CLUSTER} --dir ~/.kube/${CLUSTER} --output-certs --use-certificate --force
done

After doing do, I will get the subfolders and each their ssl and config files in. Now I know merging is possible into one file, yet would be great if kui could seek also in subfolders for config files. a rule in form/.kube/*/config cannot be so hard to be made or?

Now back to the context issue.

Each config file has set default context. Thus making Kui at opening unable to render the remaining context, unless any other is explicitly set in place of default. The namespaces are not expandable under @ .

[myan9]

Hi @uhlhosting! Thanks for the issue report! I’m not sure if I understood your issue correctly… Is your issue saying Kui won’t render @ namespace at the bottom status stripe unless the default context defines namespace in the kube config files? Please correct me if I misunderstood the issue. Thanks!

[myan9]

Hi @uhlhosting! Thanks for clarifying the issue! We could enhance Kui by always rendering @ default for empty namespace config. However, I feel like maybe Kui shouldn’t render the @ if it can’t find one. Just like the command kubectl config get-contexts, it shows empty spot for empty namespace config. Actually, you can still select namespace for your cluster with command kubectl get ns. I have a PR to remove the empty @, please feel free to tell us your thoughts. Thanks!