kubernetes/kops · error

error creating PoolHealthCheck: %v

Error message

error creating PoolHealthCheck: %v

What it means

Wrapped error from PoolHealthCheck.RenderGCE when the TargetPools.AddHealthCheck call fails while attaching a health check to a target pool (a == nil). The %v carries the GCE rejection — commonly an invalid health-check self-link or a missing target pool.

Source

Thrown at upup/pkg/fi/cloudup/gcetasks/poolhealthcheck.go:100

}

func (_ *PoolHealthCheck) CheckChanges(a, e, changes *PoolHealthCheck) error {
	return nil
}

func (p *PoolHealthCheck) RenderGCE(t *gce.GCEAPITarget, a, e, changes *PoolHealthCheck) error {
	if a == nil {
		targetPool := fi.ValueOf(p.Pool.Name)
		req := &compute.TargetPoolsAddHealthCheckRequest{
			HealthChecks: []*compute.HealthCheckReference{
				{
					HealthCheck: p.Healthcheck.SelfLink,
				},
			},
		}
		op, err := t.Cloud.Compute().TargetPools().AddHealthCheck(t.Cloud.Project(), t.Cloud.Region(), targetPool, req)
		if err != nil {
			return fmt.Errorf("error creating PoolHealthCheck: %v", err)
		}

		if err := t.Cloud.WaitForOp(op); err != nil {
			return fmt.Errorf("error creating PoolHealthCheck: %v", err)
		}
	}
	return nil
}

func (_ *PoolHealthCheck) RenderTerraform(t *terraform.TerraformTarget, a, e, changes *PoolHealthCheck) error {
	return nil
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Verify the referenced health check exists and its SelfLink is valid for the project
2. Confirm the target pool exists in the region before attach
3. Inspect the wrapped error and re-run after fixing the underlying issue

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/gcetasks/poolhealthcheck.go:100 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/28411a93a9d249f3. Report an issue: GitHub.