kubernetes/kops · error

getting Loadbalancer for API Ingress Status: %w

Error message

getting Loadbalancer for API Ingress Status: %w

What it means

Listing load balancers in the cluster resource group failed while GetApiIngressStatus tried to determine the API endpoint address. Fires on ARM API errors, wrong resource group, or missing permissions.

Source

Thrown at upup/pkg/fi/cloudup/azure/azure_cloud.go:275

}

// AddClusterTags adds cluster tags to the resource.
func (c *azureCloudImplementation) AddClusterTags(tags map[string]*string) {
	for k, v := range c.tags {
		tags[k] = &v
	}
}

func (c *azureCloudImplementation) GetApiIngressStatus(cluster *kops.Cluster) ([]fi.ApiIngressStatus, error) {
	var ingresses []fi.ApiIngressStatus
	rg := cluster.AzureResourceGroupName()

	lbSpec := cluster.Spec.API.LoadBalancer
	if lbSpec != nil {
		// Get load balancers in cluster resource group
		lbs, err := c.loadBalancersClient.List(context.TODO(), rg)
		if err != nil {
			return nil, fmt.Errorf("getting Loadbalancer for API Ingress Status: %w", err)
		}

		for _, lb := range lbs {
			val := lb.Tags[TagClusterName]
			if val == nil || *val != cluster.Name {
				continue
			}
			if lb.Properties == nil {
				continue
			}
			for _, i := range lb.Properties.FrontendIPConfigurations {
				if i.Properties == nil {
					continue
				}
				switch lbSpec.Type {
				case kops.LoadBalancerTypeInternal:
					if i.Properties.PrivateIPAddress == nil {
						continue

View on GitHub (pinned to 4c8573c808)

Solutions

1. Verify the cluster's Azure resource group name is correct and exists
2. Check the credential's permissions on the resource group
3. Retry after transient ARM failures

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/azure/azure_cloud.go:275 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/3778b5cb882afe28. Report an issue: GitHub.