Commit 68c9a19
[kustomize_deploy] Fix MetalLB CR creation race with webhook readiness
The MetalLB validating webhook can reject CR creation with "no endpoints
available" when the operator's webhook services aren't fully ready yet.
The existing deployment availability checks pass before the backing
Endpoints objects have addresses populated, creating a window where
CR creation fails.
Add an explicit wait for all four MetalLB webhook endpoint services
(metallb-operator-controller-manager-service,
metallb-operator-webhook-server-service,
metallb-operator-webhook-service, webhook-service) to have at least
one ready address before applying MetalLB CRs. Also add retry logic
(retries: 10, delay: 15) to the CR apply step itself as a safety net
for any remaining transient webhook failures.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Roberto Alfieri <ralfieri@redhat.com>1 parent 52e11d1 commit 68c9a19
1 file changed
Lines changed: 26 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
325 | 325 | | |
326 | 326 | | |
327 | 327 | | |
| 328 | + | |
| 329 | + | |
| 330 | + | |
| 331 | + | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
| 336 | + | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
| 341 | + | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
| 349 | + | |
328 | 350 | | |
329 | 351 | | |
330 | 352 | | |
| |||
374 | 396 | | |
375 | 397 | | |
376 | 398 | | |
| 399 | + | |
| 400 | + | |
| 401 | + | |
| 402 | + | |
377 | 403 | | |
378 | 404 | | |
379 | 405 | | |
| |||
0 commit comments