kubernetes/kops · error

creating load-balancer: %w

Error message

creating load-balancer: %w

What it means

In the load-balancer task's RenderScw, lbService.CreateLB failed while provisioning a new API load-balancer with the default type. Nothing was created; the wrapped error is the SDK response — quota, invalid zone, permissions, or name conflict.

Source

Thrown at upup/pkg/fi/cloudup/scalewaytasks/loadbalancer.go:189

				return fmt.Errorf("updatings tags for load-balancer %q: %w", fi.ValueOf(expected.Name), err)
			}
		}

		expected.LBID = actual.LBID
		expected.LBAddresses = actual.LBAddresses

	} else {

		klog.Infof("Creating new load-balancer with name %q", fi.ValueOf(expected.Name))

		lbCreated, err := lbService.CreateLB(&lb.ZonedAPICreateLBRequest{
			Zone: scw.Zone(fi.ValueOf(expected.Zone)),
			Name: fi.ValueOf(expected.Name),
			Type: LbDefaultType,
			Tags: expected.Tags,
		})
		if err != nil {
			return fmt.Errorf("creating load-balancer: %w", err)
		}

		_, err = lbService.WaitForLb(&lb.ZonedAPIWaitForLBRequest{
			LBID: lbCreated.ID,
			Zone: scw.Zone(fi.ValueOf(expected.Zone)),
		})
		if err != nil {
			return fmt.Errorf("waiting for load-balancer %s: %w", lbCreated.ID, err)
		}

		lbIPs := []string(nil)
		for _, ip := range lbCreated.IP {
			lbIPs = append(lbIPs, ip.IPAddress)
		}
		expected.LBID = &lbCreated.ID
		expected.LBAddresses = lbIPs

	}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check the wrapped error (LB quota limits are common)
2. Verify the zone supports load-balancers
3. Free quota or adjust limits, then retry the apply

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/scalewaytasks/loadbalancer.go:189 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/e48a0c8632a4e5f8. Report an issue: GitHub.