Too many aws clients constructed

[anvouk]

What happened?

After deploying a decent number of deployments devspace starts to spam the following:

.W0923 12:44:16.108460   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1116 clients constructed calling "aws"
/W0923 12:44:16.108993   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1117 clients constructed calling "aws"
cW0923 12:44:16.110711   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1118 clients constructed calling "aws"
hW0923 12:44:16.111459   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1119 clients constructed calling "aws"
aW0923 12:44:16.112473   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1120 clients constructed calling "aws"
rtW0923 12:44:16.114245   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availa
ble network connections; 1121 clients constructed calling "aws"
sW0923 12:44:16.115653   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1122 clients constructed calling "aws"
/zooW0923 12:44:16.117460   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust avai
lable network connections; 1123 clients constructed calling "aws"
keeW0923 12:44:16.118716   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust avail
able network connections; 1124 clients constructed calling "aws"
peW0923 12:44:16.120500   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availa
ble network connections; 1125 clients constructed calling "aws"
r-W0923 12:44:16.120931   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availa
ble network connections; 1126 clients constructed calling "aws"
uW0923 12:44:16.121564   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1127 clients constructed calling "aws"
i (W0923 12:44:16.121564   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust avail
able network connections; 1128 clients constructed calling "aws"
zW0923 12:44:16.126541   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1129 clients constructed calling "aws"
oW0923 12:44:16.127191   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availab
le network connections; 1130 clients constructed calling "aws"
okW0923 12:44:16.127689   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availa
ble network connections; 1131 clients constructed calling "aws"
[wait] \ Deploying chart ./charts/zookeeper-ui (zookeeper-ui) with helm (0s)W0923 12:44:16.309463   14756 exec.go:203] constructing many client instances from the same exec auth config
can cause performance problems during cert rotation and can exhaust available network connections; 1132 clients constructed calling "aws"
[wait] / Deploying chart ./charts/zookeeper-ui (zookeeper-ui) with helm (0s)W0923 12:44:16.702462   14756 exec.go:203] constructing many client instances from the same exec auth config
can cause performance problems during cert rotation and can exhaust available network connections; 1133 clients constructed calling "aws"
[wait] / Deploying chart ./charts/zookeeper-ui (zookeeper-ui) with helm (2s)W0923 12:44:17.881189   14756 exec.go:203] constructing many client instances from the same exec auth config
can cause performance problems during cert rotation and can exhaust available network connections; 1134 clients constructed calling "aws"
W0923 12:44:17.886191   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1135 clients constructed calling "aws"
W0923 12:44:17.887748   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1136 clients constructed calling "aws"
W0923 12:44:17.889231   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1137 clients constructed calling "aws"
W0923 12:44:17.898302   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1138 clients constructed calling "aws"
W0923 12:44:17.900188   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1139 clients constructed calling "aws"
W0923 12:44:17.901575   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1140 clients constructed calling "aws"
W0923 12:44:17.902209   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1141 clients constructed calling "aws"
W0923 12:44:17.906194   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1142 clients constructed calling "aws"
W0923 12:44:17.907447   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1143 clients constructed calling "aws"
[done] √ Deployed helm chart (Release revision: 0)
[done] √ Successfully deployed zookeeper-ui with helm
W0923 12:44:18.668731   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1144 clients constructed calling "aws"
W0923 12:44:18.669732   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1145 clients constructed calling "aws"
W0923 12:44:18.669732   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1146 clients constructed calling "aws"
W0923 12:44:18.670733   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1147 clients constructed calling "aws"
W0923 12:44:18.672296   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1148 clients constructed calling "aws"
W0923 12:44:18.672733   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1149 clients constructed calling "aws"
W0923 12:44:18.673735   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1150 clients constructed calling "aws"
W0923 12:44:18.674024   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1151 clients constructed calling "aws"
W0923 12:44:18.674401   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1152 clients constructed calling "aws"
W0923 12:44:18.675028   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1153 clients constructed calling "aws"
W0923 12:44:18.675731   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1154 clients constructed calling "aws"
W0923 12:44:18.676818   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1155 clients constructed calling "aws"
W0923 12:44:18.676818   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1156 clients constructed calling "aws"
W0923 12:44:18.677249   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1157 clients constructed calling "aws"
W0923 12:44:18.677730   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1158 clients constructed calling "aws"
W0923 12:44:18.677730   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1159 clients constructed calling "aws"
W0923 12:44:18.678731   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1160 clients constructed calling "aws"
W0923 12:44:18.679288   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1161 clients constructed calling "aws"
W0923 12:44:18.679730   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1162 clients constructed calling "aws"
W0923 12:44:18.681985   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1163 clients constructed calling "aws"
W0923 12:44:18.684617   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1164 clients constructed calling "aws"
W0923 12:44:18.684732   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1165 clients constructed calling "aws"
W0923 12:44:18.684732   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1166 clients constructed calling "aws"
W0923 12:44:18.686071   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1167 clients constructed calling "aws"
W0923 12:44:18.686071   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1168 clients constructed calling "aws"
W0923 12:44:18.687110   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1169 clients constructed calling "aws"
W0923 12:44:18.687732   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1170 clients constructed calling "aws"
W0923 12:44:18.688009   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1171 clients constructed calling "aws"
W0923 12:44:18.689754   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1172 clients constructed calling "aws"
W0923 12:44:18.690824   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1173 clients constructed calling "aws"
W0923 12:44:18.693730   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1174 clients constructed calling "aws"
W0923 12:44:18.694764   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1175 clients constructed calling "aws"
W0923 12:44:18.695733   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1176 clients constructed calling "aws"
W0923 12:44:18.696861   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1177 clients constructed calling "aws"
W0923 12:44:18.697735   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1178 clients constructed calling "aws"
W0923 12:44:18.697735   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1179 clients constructed calling "aws"
W0923 12:44:18.697735   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1180 clients constructed calling "aws"
W0923 12:44:18.698845   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1181 clients constructed calling "aws"
W0923 12:44:18.698845   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1182 clients constructed calling "aws"
W0923 12:44:18.699829   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1183 clients constructed calling "aws"
W0923 12:44:18.699829   14756 exec.go:203] constructing many client instances from the same exec auth config can cause performance problems during cert rotation and can exhaust availabl
e network connections; 1184 clients constructed calling "aws"

What did you expect to happen instead?
Some way to limit the number of concurrent aws clients constructed and/or remove the super spamming warning.

Note: the deployments still succeeds as expected.

How can we reproduce the bug? (as minimally and precisely as possible)
under the deployments section of devspace.yaml put a good number of deployments and use aws as provider.

Local Environment:

• DevSpace Version: 5.0.3
• Operating System: windows 10
• Deployment method: helm and kubectl apply

Kubernetes Cluster:

• Cloud Provider: aws
• Kubernetes Version: 1.16
• kubectl version: Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"windows/amd64"} Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.13-eks-2ba888", GitCommit:"2ba888155c7f8093a1bc06e3336333fbdb27b3da", GitTreeState:"clean", BuildDate:"2020-07-17T18:48:53Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?

/kind bug

[FabianKramm]

@QwertyQaz414 thanks for reporting this issue! I'll take a look at this and push a fix as soon as possible

[FabianKramm]

@anvouk this should be fixed with v5.1.0