🚸 ux(kube): use id_or_name as primary field / missing flags in cluster kubeconfig#249
Conversation
|
WARNING : Differences in reference doc 🤔 Detailed changesdocs/reference/octl_kube_cluster.md docs/reference/octl_kube_cluster_delete.md docs/reference/octl_kube_cluster_describe.md docs/reference/octl_kube_cluster_kubeconfig.md docs/reference/octl_kube_cluster_update.md docs/reference/octl_kube_project.md docs/reference/octl_kube_project_clusters.md docs/reference/octl_kube_project_delete.md docs/reference/octl_kube_project_describe.md docs/reference/octl_kube_project_nets.md docs/reference/octl_kube_project_public-ips.md docs/reference/octl_kube_project_quotas.md docs/reference/octl_kube_project_snapshots.md docs/reference/octl_kube_project_update.md docs/reference/octl_kube_publicip.md docs/reference/octl_kube_publicip_describe.md |
|
Binary size: 82.2MB => 82.2MB (change +0KB, +0.0%) 😉 |
Description
This PR configures the kube usage to specify that names can be used as well as ids.
It also adds missing flags in cluster kubeconfig.
Type of Change
Please check the relevant option(s):
How Has This Been Tested?
Please describe the test strategy:
Checklist
Additional Context