Skip to content

CSV Field Markers are not collected if they are in another go file #3744

@shivanshs9

Description

@shivanshs9

Bug Report

What did you do?
In my operator project, CRD status struct is in another go file, called <CRD>_status.go. I've annotated some of its fields with operator-sdk CSV markers, like:

type ClusterStatus struct {
	// +operator-sdk:csv:customresourcedefinitions:type=status,displayName="Phase",xDescriptors="urn:alm:descriptor:io.kubernetes.phase"
	Phase ClusterPhase `json:"phase"`
	// [other fields]
}

Then I ran make bundle to generate the bundle manifests.

What did you expect to see?
The generated CSV would have both specDescriptors and statusDescriptors for this API.

What did you see instead? Under which circumstances?
The generated CSV only has the specDescriptors of this API and no statusDescriptors field.

Environment

operator-sdk version
operator-sdk version: "v1.0.0", commit: "d7d5e0cd6cf5468bb66e0849f08fda5bf557f4fa", kubernetes version: "v1.18.2", go version: "go1.13.11 linux/amd64", GOOS: "linux", GOARCH: "amd64"
  • operator-sdk version: v1.0.0
  • go version: go1.13.11
  • Kubernetes version information: v1.18.2
  • Kubernetes cluster kind:

  • Are you writing your operator in ansible, helm, or go? go

Possible Solution

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.language/goIssue is related to a Go operator projectolm-integrationIssue relates to the OLM integration

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions