locksmithcl/locksmithcl: fix defaultEnpoints

Using etcd/v3, it seems we don't need to specify the scheme (`http`/`https`). If it's specified, it will use the ones provided by default and stick to it - even if it's HTTP and we have a HTTPS configured etcd. So it will fail because we send http request to a https service Signed-off-by: Mathieu Tortuyaux <[email protected]>
flatcar · Aug 31, 2021 · bbd12cd · bbd12cd
1 parent cbcacee
commit bbd12cd
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/locksmithctl/locksmithctl.go b/locksmithctl/locksmithctl.go
@@ -55,8 +55,8 @@ var (
 	}{}
 
 	defaultEndpoints = []string{
-		"http://127.0.0.1:2379",
-		"http://127.0.0.1:4001",
+		"127.0.0.1:2379",
+		"127.0.0.1:4001",
 	}
 )