kubernetes/kops · error

error parsing channel %q: %v

Error message

error parsing channel %q: %v

What it means

After the channel bytes are read successfully, LoadChannel hands them to ParseChannel. This error means the file was fetched but its content could not be parsed as a kOps channel YAML document. The wrapped %v carries the YAML/schema detail (bad indentation, unknown fields in strict mode, wrong root kind).

Source

Thrown at pkg/apis/kops/channel.go:150

	resolvedURL, err := ResolveChannel(location)
	if err != nil {
		return nil, err
	}

	if resolvedURL == nil {
		return &Channel{}, nil
	}

	resolved := resolvedURL.String()

	klog.V(2).Infof("Loading channel from %q", resolved)
	channelBytes, err := vfsContext.ReadFile(resolved)
	if err != nil {
		return nil, fmt.Errorf("error reading channel %q: %v", resolved, err)
	}
	channel, err := ParseChannel(channelBytes)
	if err != nil {
		return nil, fmt.Errorf("error parsing channel %q: %v", resolved, err)
	}
	klog.V(4).Infof("Channel contents: %s", string(channelBytes))

	return channel, nil
}

// ParseChannel parses a Channel object
func ParseChannel(channelBytes []byte) (*Channel, error) {
	channel := &Channel{}
	err := ParseRawYaml(channelBytes, channel)
	if err != nil {
		return nil, fmt.Errorf("error parsing channel %v", err)
	}

	return channel, nil
}

// FindRecommendedUpgrade returns a string with a new version, if the current version is out of date

View on GitHub (pinned to 4c8573c808)

Solutions

1. curl the resolved channel URL and inspect the body — if it is HTML or empty, fix the URL/network path first.
2. Validate the channel file YAML syntax (yamllint) and that it declares the expected Channel apiVersion/kind.
3. If the channel is custom, start from the upstream channel file as a template and re-apply edits carefully.
4. Check for proxy/captive-portal interference returning error pages with HTTP 200.

Example fix

// before (channel.yaml)
kind: Channle
spec: {}
// after
apiVersion: kops.k8s.io/v1alpha1
kind: Channel
spec:
  kubernetesVersion:
    recommendedVersion: 1.28.3

var probe map[string]interface{}
if err := yaml.Unmarshal(channelBytes, &probe); err != nil {
    return fmt.Errorf("not valid YAML: %w", err)
}
if probe["kind"] != "Channel" {
    return fmt.Errorf("unexpected kind %v; is the URL returning HTML?", probe["kind"])
}

func looksLikeChannel(b []byte) bool {
    var c kops.Channel
    return yaml.Unmarshal(b, &c) == nil && c.Kind == "Channel"
}

channel, err := kops.LoadChannel(vfsContext, location)
if err != nil && strings.Contains(err.Error(), "error parsing channel") {
    // log first 200 bytes of the body for diagnosis, then fail fast
}

When it happens

Trigger: LoadChannel where ParseChannel(channelBytes) fails: the URL points to an HTML error page, an empty file, or a YAML document that does not match the Channel schema (wrong apiVersion/kind, malformed YAML).

Common situations: A proxy or captive portal returns an HTML 200 page instead of YAML; a hand-edited channel file with a YAML syntax error; channel file saved with wrong content (e.g. a cluster spec pasted in); truncated download.

Related errors

• unable to unmarshall content from template: %s, error: %s
• error parsing channel %v
• error parsing configuration: %v
• failed to parse manifest: %w
• error parsing addons or manifest: %v

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