Commit db550bb
authored
fix(e2e): carry the kubeconfig into the partial-cluster delete
Review feedback on kube-logging#2301. The delete that clears a half-built cluster after a
create times out did not name the kubeconfig the create used, so it fell back to
the shared default. That is the delete most likely to lose the lock, because it
runs exactly when several creates are timing out together.
The stalled-create case creates with a kubeconfig now, so the delete's arguments
are pinned rather than only its presence: without the fix it reports
`delete cluster --name stuck` against the expected
`delete cluster --kubeconfig /tmp/kind-stuck.kubeconfig --name stuck`.
Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>1 parent a314e11 commit db550bb
2 files changed
Lines changed: 18 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
110 | 110 | | |
111 | 111 | | |
112 | 112 | | |
113 | | - | |
114 | | - | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
| 119 | + | |
115 | 120 | | |
116 | 121 | | |
117 | 122 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
266 | 266 | | |
267 | 267 | | |
268 | 268 | | |
269 | | - | |
| 269 | + | |
| 270 | + | |
| 271 | + | |
270 | 272 | | |
271 | 273 | | |
272 | 274 | | |
273 | | - | |
274 | | - | |
275 | | - | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
276 | 283 | | |
277 | 284 | | |
278 | 285 | | |
| |||
0 commit comments