A CSV is used to provide information about the operator to OLM (operator lifecycle manager). As of now we are missing a lot of information about the test-operator in the CSV in comparison with the rest the operators ([1] vs [2]). The CSV contains information that are facing the customer therefore it would be appropriate to at least add:

• all the parameters that are part of the Tempest (Tobiko, Horizon, ...) CRD
• provider (Red Hat)
• version
• keywords
• correct description
• icon

Good to know:

• Some of the fields in the CSV can be probably generated with `make bundle`.
• If you want to use `make bundle` to generate the values in customresourcedefinitions (recommended way because this will allow us to update the CSV automatically later!) then you need to add this line [3] to all parameters in this folder [4].

DoD:

• The test-operator CSV contains all the information mentioned above.

PRs:

• https://github.com/openstack-k8s-operators/test-operator/pull/111

[1] https://github.com/openstack-k8s-operators/test-operator/blob/main/config/manifests/bases/test-operator.clusterserviceversion.yaml
[2] https://github.com/openstack-k8s-operators/openstack-operator/blob/main/config/manifests/bases/openstack-operator.clusterserviceversion.yaml
[3] https://github.com/openstack-k8s-operators/openstack-operator/blob/9351c6f223b4f8bf5785768f7e5a2269d1e76d22/apis/core/v1beta1/openstackcontrolplane_types.go#L86
[4] https://github.com/openstack-k8s-operators/test-operator/tree/main/api/v1beta1