kubernetes/kops · error

linode cloud provider currently supports one region only

Error message

linode cloud provider currently supports one region only

What it means

setupZones (Linode branch) validation: fires when more than one zone is given. Akamai (Linode) zones map to regions and the provider supports only one region per kOps cluster, so multi-zone input is rejected before subnet mapping.

Source

Thrown at upup/pkg/fi/cloudup/new_cluster.go:791

		// for DO, subnets are just regions
		subnetName := region

		if subnet == nil {
			subnet = &api.ClusterSubnetSpec{
				Name: subnetName,
				// region and zone are the same for DO
				Region: region,
				Zone:   region,
			}
			cluster.Spec.Networking.Subnets = append(cluster.Spec.Networking.Subnets, *subnet)
		}
		zoneToSubnetsMap[region] = append(zoneToSubnetsMap[region], subnet)
		return zoneToSubnetsMap, nil

	case api.CloudProviderLinode:
		if len(opt.Zones) > 1 {
			return nil, fmt.Errorf("linode cloud provider currently supports one region only")
		}

		// For Akamai (Linode) we pass regions via --zones.
		region := opt.Zones[0]
		subnet := model.FindSubnet(cluster, region)

		if subnet == nil {
			subnet = &api.ClusterSubnetSpec{
				Name:   region,
				Region: region,
				Zone:   region,
			}
			cluster.Spec.Networking.Subnets = append(cluster.Spec.Networking.Subnets, *subnet)
		}
		zoneToSubnetsMap[region] = append(zoneToSubnetsMap[region], subnet)
		return zoneToSubnetsMap, nil

	case api.CloudProviderHetzner:

View on GitHub (pinned to 4c8573c808)

Solutions

  1. Pass a single --zones value (one Linode region)
  2. Split multi-region deployments into separate clusters
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/new_cluster.go:791 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/50e8e07f3a5d583e. Report an issue: GitHub.