Default contexts and /.kube subfolders?
See original GitHub issueHi,
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 @ .
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Default contexts and /.kube subfolders? · Issue #4274 - GitHub
Hi, By default my config files generated by magnum/openstack for kubernetes are in a config file I export these with: for CLUSTER in ......
Read more >Kubernetes Cluster Access: Authenticate and Authorize an ...
The following commands can be used to get information about the contexts and users. The default user here is called minikube.
Read more >Managing Resources | Kubernetes
Kubernetes provides a number of tools to help you manage your application deployment, including scaling and updating.
Read more >Use Kubernetes service accounts to enable automated ...
One easy way to get a full list of resources and subresources that are available on a cluster is to look at the...
Read more >How Do You Make Kubernetes Config Files Not Suck?
By default, the kubeconfig files will be merged or written into your ~/.kube/config file, or if you have a $KUBECONFIG variable set, into...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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!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 commandkubectl config get-contexts
, it shows empty spot for empty namespace config. Actually, you can still select namespace for your cluster with commandkubectl get ns
. I have a PR to remove the empty@
, please feel free to tell us your thoughts. Thanks!