Skip to content

When a CRD is present in a bundle, but not referenced in the CRD, confusing error about mismatched versions occurs. #172

@flickerfly

Description

@flickerfly

I upgraded a CSV and copied in the CRDs. I had one that isn't mentioned in the CSV in the folder with a spec.version that mentioned a previous version. operator-courier verify would complain

ERROR: CRD.spec.version does not match CSV.spec.crd.owned.version

This confused me for awhile until I realized the other CRD was in the directory and removed it to clear the error.

Two suggestions:

  1. As there can be multiple CRDs on an operator, could the CRD in conflict with the CSV be mentioned by some identifier like name?
  2. Alert on a CRD not mentioned in the CSV

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions