The operator-sdk will generate most of the pieces of information you will need to get through certification, though some manual adjustments will need to be made.
In YAML, you don't need to place key names in any specific order, as long as the keys stay at the proper indentation level
Editing the CSV
Below is a list of other changes you need to make to the CSV as the command will not automatically create these necessary bits.
Fields to add under metadata.annotations
categories - Comma separated string of these applicable category names
description - Short description of the operator
containerImage - The full location (registry, repository, name and tag) of the operator image
createdAt - A rough (to the day) timestamp of when the operator image was created
support - Name of the supporting vendor (eg: ExampleCo)
repository - URL of the operator's source code repository (this field is optional)
The annotations above have been truncated to show you where the fields need to be added
Fields to adjust under spec
The Operator-SDK will generate the following fields but you will need to adjust them for certification
description - Long description of the operator's owned customresourcedefinitions in Markdown format. Usage instructions and relevant info for the user goes here
icon.base64data - A base64 encoded PNG, JPEG or SVG image will need to be added
icon.medatype - The corresponding MIME type of the image (eg: image/png)
The base64data was truncated in the example above to show you placement