-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSV Field Markers are not collected if they are in another go file #3744
Comments
@shivanshs9 is type Cluster struct {
v1.TypeMeta `json:",inline"`
v1.ObjectMeta `json:"metadata,omitempty"`
ClusterSpec `json:"spec,omitempty"`
ClusterStatus `json:"status,omitempty"`
} |
@estroz Yes, it is indeed referred there. Plus, the CSV works in OpenShift when I manually add the statusDescriptors after generating it. |
@shivanshs9 does the scenario in #4196 describe the yours as well? |
@estroz not exactly, since in my case, only |
We are also suffering from this problem, We have a number of common structures (in a This is causing us a major head-ache because we can't share structures across multiple CRDs meaning we need to duplicate lots of code. |
Reopening this as it has not been resolved by #4445 |
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:Then I ran
make bundle
to generate the bundle manifests.What did you expect to see?
The generated CSV would have both
specDescriptors
andstatusDescriptors
for this API.What did you see instead? Under which circumstances?
The generated CSV only has the
specDescriptors
of this API and nostatusDescriptors
field.Environment
operator-sdk version
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.
The text was updated successfully, but these errors were encountered: