summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIgor D.C <igor.duarte.cardoso@intel.com>2020-10-08 23:50:55 +0000
committerIgor D.C <igor.duarte.cardoso@intel.com>2020-10-08 23:55:37 +0000
commitedaf4416c5002254b60199a0b9710ebb23ccdf7b (patch)
tree6a46621b028f1de815a8cc31948ec41a2788e40a
parent8ad373936c2438a06fd02202c507e3ceadbacea6 (diff)
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 <igor.duarte.cardoso@intel.com>
-rw-r--r--src/dcm/pkg/module/cluster.go2
1 files changed, 1 insertions, 1 deletions
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"`
}