kubernetes/kops · error

Error creating load balancer with Name=%s, Error=%v

Error message

Error creating load balancer with Name=%s, Error=%v

What it means

The DigitalOcean LoadBalancer task's RenderDO wraps the LoadBalancersService.Create failure. It fires when the DO API rejects load-balancer creation (invalid forwarding rules, region/tag mismatch, quota, permissions); the LB name and underlying error are logged/returned so the apply fails and retries.

Source

Thrown at upup/pkg/fi/cloudup/dotasks/loadbalancer.go:194

		vpcUUID, err = t.Cloud.GetVPCUUID(fi.ValueOf(e.NetworkCIDR), fi.ValueOf(e.VPCName))
		if err != nil {
			return fmt.Errorf("Error fetching vpcUUID from network cidr=%s", fi.ValueOf(e.NetworkCIDR))
		}
	} else if fi.ValueOf(e.VPCUUID) != "" {
		vpcUUID = fi.ValueOf(e.VPCUUID)
	}

	loadBalancerService := t.Cloud.LoadBalancersService()
	loadbalancer, _, err := loadBalancerService.Create(context.TODO(), &godo.LoadBalancerRequest{
		Name:            fi.ValueOf(e.Name),
		Region:          fi.ValueOf(e.Region),
		Tag:             fi.ValueOf(e.DropletTag),
		VPCUUID:         vpcUUID,
		ForwardingRules: Rules,
		HealthCheck:     HealthCheck,
	})
	if err != nil {
		return fmt.Errorf("Error creating load balancer with Name=%s, Error=%v", fi.ValueOf(e.Name), err)
	}

	e.ID = new(loadbalancer.ID)
	e.IPAddress = new(loadbalancer.IP) // This will be empty on create, but will be filled later on FindAddresses invokation.

	klog.V(2).Infof("load balancer for DO created with id: %s", loadbalancer.ID)
	return nil
}

// GetWellKnownServices implements fi.HasAddress::GetWellKnownServices.
// It indicates which services we support with this load balancer.
func (lb *LoadBalancer) GetWellKnownServices() []wellknownservices.WellKnownService {
	return lb.WellKnownServices
}

func (lb *LoadBalancer) FindAddresses(c *fi.CloudupContext) ([]string, error) {
	cloud := c.T.Cloud.(do.DOCloud)
	loadBalancerService := cloud.LoadBalancersService()

View on GitHub (pinned to 4c8573c808)

Solutions

  1. Inspect the wrapped DO API error for the rejection reason
  2. Verify forwarding rules, health check, region, and VPC settings
  3. Check LB quota for the account
  4. Retry after fixing the configuration
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/dotasks/loadbalancer.go:194 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/d9bd75b41a8a8b61. Report an issue: GitHub.