correct version, provider and name

[alexxa]

I have just tried to deploy cna-operator following ReadMe - Deploy using OLM and using this image.
In the Web UI, I see that

• There is no 'Operator' in the name in Operators Catalog. I don't know if there is any spec for operators naming and if it should be there or not.
• version 0.0.0
• "provided by KubeVirt project". Should it be "Red Hat", maybe?
  

[phoracek]

Thanks for reporting this @alexxa.

@SchSeba if you find some time, would you please look into it? For the name, we should check on KubeVirt and CDI operators, it there is an agreement on ' Operator'. The same for 'provided by'.

The problem with the version is, that the cna-registry is outdated (22 days old). @alexxa could you try to use https://quay.io/repository/kubevirt/cluster-network-addons-registry?tab=tags? With 0.5.0 tag.

[SchSeba]

I will take a look on that

btw I am unfamiliar with the image you used https://hub.docker.com/r/djzager/cna-registry/tags
@phoracek ?

Our images are under quay.io inside the kubevirt organization.

[SchSeba]

I check the HCO and there is the file https://github.com/kubevirt/hyperconverged-cluster-operator/pull/46/files#diff-d18084c4431837e68157c7948d3b17b9R28

they use publisher: Red Hat same as us

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[phoracek]

/remove-lifecycle stale

Should be verified.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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/test-infra repository.