Skip to content

OCPBUGS-65849: Add descriptions to owned CRDs in CSV#1000

Merged
openshift-merge-bot[bot] merged 4 commits intonextfrom
OCPBUGS-65849-add-crd-descriptions
Mar 4, 2026
Merged

OCPBUGS-65849: Add descriptions to owned CRDs in CSV#1000
openshift-merge-bot[bot] merged 4 commits intonextfrom
OCPBUGS-65849-add-crd-descriptions

Conversation

@harche
Copy link
Contributor

@harche harche commented Feb 25, 2026

Summary

  • The OpenShift console shows "Not available" for DASOperator, AllocationClaim, and NodeAccelerator on the Operator details page because the description field is missing from spec.customresourcedefinitions.owned entries in the CSV.
  • Added description fields to all three owned CRD entries in bundle-ocp/manifests/das-operator.clusterserviceversion.yaml.

Details

The console reads crd.description from the CSV and passes it to a MarkdownView component (clusterserviceversion.tsx#L870). When undefined, SyncMarkdownView falls back to "Not available" (markdown-view.tsx#L14).

Jira: https://issues.redhat.com/browse/OCPBUGS-65849

Test plan

  • Build bundle image with the updated CSV
  • Regenerate FBC catalog using ./generate-fbc.sh in the FBC repo
  • Install the operator on an OCP cluster and verify the Operator details page shows the descriptions instead of "Not available"

🤖 Generated with Claude Code

The OpenShift console shows "Not available" for DASOperator,
AllocationClaim, and NodeAccelerator on the Operator details page
because the description field is missing from the owned CRD entries
in the ClusterServiceVersion.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Feb 25, 2026
@openshift-ci-robot
Copy link

@harche: This pull request references Jira Issue OCPBUGS-65849, which is valid.

No validations were run on this bug
Details

In response to this:

Summary

  • The OpenShift console shows "Not available" for DASOperator, AllocationClaim, and NodeAccelerator on the Operator details page because the description field is missing from spec.customresourcedefinitions.owned entries in the CSV.
  • Added description fields to all three owned CRD entries in bundle-ocp/manifests/das-operator.clusterserviceversion.yaml.

Details

The console reads crd.description from the CSV and passes it to a MarkdownView component (clusterserviceversion.tsx#L870). When undefined, SyncMarkdownView falls back to "Not available" (markdown-view.tsx#L14).

Jira: https://issues.redhat.com/browse/OCPBUGS-65849

Test plan

  • Build bundle image with the updated CSV
  • Regenerate FBC catalog using ./generate-fbc.sh in the FBC repo
  • Install the operator on an OCP cluster and verify the Operator details page shows the descriptions instead of "Not available"

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 25, 2026
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 25, 2026
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2026
@harche
Copy link
Contributor Author

harche commented Feb 25, 2026

/test e2e-bundle-runc

- kind: DASOperator
name: dasoperators.inference.redhat.com
version: v1alpha1
description: DASOperator is the Schema for the DASOperator API
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each description has a different style.

Can we make these all consistent?

harche and others added 3 commits February 25, 2026 21:26
Co-authored-by: Kevin Hannon <kehannon@redhat.com>
Co-authored-by: Kevin Hannon <kehannon@redhat.com>
Co-authored-by: Kevin Hannon <kehannon@redhat.com>
@harche
Copy link
Contributor Author

harche commented Feb 26, 2026

GPU quota issue, trying again,

/test e2e-bundle-runc

@harche
Copy link
Contributor Author

harche commented Mar 2, 2026

/test e2e-bundle-runc

@openshift-ci
Copy link

openshift-ci bot commented Mar 2, 2026

@harche: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@harche
Copy link
Contributor Author

harche commented Mar 2, 2026

/cc @kannon92 for review.

Copy link
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, sairameshv

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit cb08664 into next Mar 4, 2026
15 checks passed
@harche harche deleted the OCPBUGS-65849-add-crd-descriptions branch March 4, 2026 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants