From edaf4416c5002254b60199a0b9710ebb23ccdf7b Mon Sep 17 00:00:00 2001 From: "Igor D.C" Date: Thu, 8 Oct 2020 23:50:55 +0000 Subject: Fix mispelled key name in kubeconfig Fixes the mispelled "currentcontext" with the right key name "current-context" which was introduced as a regression with or before the latest version of the kubeconfig code (probably a bad search/replace). This 1-character long bug was preventing the generated kubeconfigs from being correctly interpreted by kubectl. Thus, kubectl couldn't set any context of the kubeconfig as the current context. Observable output before this fix: $ kubectl get pods The connection to the server localhost:8080 was refused - did you specify the right host or port? Issue-ID: MULTICLOUD-1143 Change-Id: I617d1e20b7be2567729b84d3746b22e4ceaf8b9d Signed-off-by: Igor D.C --- src/dcm/pkg/module/cluster.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/dcm/pkg/module/cluster.go b/src/dcm/pkg/module/cluster.go index 33de7acf..9aecc6ca 100644 --- a/src/dcm/pkg/module/cluster.go +++ b/src/dcm/pkg/module/cluster.go @@ -59,7 +59,7 @@ type KubeConfig struct { Kind string `yaml:"kind"` Clusters []KubeCluster `yaml:"clusters"` Contexts []KubeContext `yaml:"contexts"` - CurrentContext string `yaml:"current-context` + CurrentContext string `yaml:"current-context"` Preferences map[string]string `yaml:"preferences"` Users []KubeUser `yaml:"users"` } -- cgit 1.2.3-korg