Create new repository for the lightspeed-operator catalog

[anik120]

$ ls | grep lightspeed-catalog
lightspeed-catalog
lightspeed-catalog-4.16
lightspeed-catalog-4.16.Dockerfile
lightspeed-catalog-4.17
lightspeed-catalog-4.17.Dockerfile
lightspeed-catalog-4.18
lightspeed-catalog-4.18.Dockerfile
lightspeed-catalog-4.19
lightspeed-catalog-4.19.Dockerfile
lightspeed-catalog-4.20
lightspeed-catalog-4.20.Dockerfile
lightspeed-catalog.Dockerfile

☝🏽 that list is only going to grow. See https://github.com/operator-framework/cool-catalog for a more maintainable way to create and maintain this catalog. TLDR: in a separate repository, there's only going to be the index.yaml file and the dockerfile, and then branched for subsequent openshift releases.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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-sigs/prow repository.