Provides an operator nested bundle for registry usage

[flickerfly]

This provides an operator bundle in the current preferred nested format so this operator can be included in registries like operatorhub.io.

Motivation & Why

I needed this for my own usage so we can deliver via an operator catalog as part of a bigger project.

What & How

Used operator-sdk to create a basic bundle under deploy/olm-catalog.

Verification Steps

Better method:

1. Add the deploy/olm-catalog/gitea-operator/ directory to your operator registry process to be included in your operator catalog
2. Run your catalog build process
3. Subscribe to the operator from the catalog

CSV check method:

1. Create your service account, crd, role and role_binding manually.
   2 Modify namespace in deploy/olm-catalog/gitea-operator/0.0.5/gitea-operator.v0.0.5.clusterserviceversion.yaml
2. kubectl/oc create -f deploy/olm-catalog/gitea-operator/0.0.5/gitea-operator.v0.0.5.clusterserviceversion.yaml

Checklist:

• Code has been tested locally by PR requester
• Changes have been successfully verified by another team member

Progress

• Finished task

[pb82]

@flickerfly Hey, thank you very much for the PR and sorry for the late response. I think it won't hurt making the operator available through OLM.

[pb82]

Should this be false?

[flickerfly]

I haven't tested that functionality yet, but I'd like it to be true. Is there a reason it needs to be false? I see use cases where having multiple gitea instances in a cluster would be beneficial.

…

On Mon, Feb 24, 2020 at 10:49 AM Peter Braun ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In deploy/olm-catalog/gitea-operator/0.0.5/gitea-operator.v0.0.5.clusterserviceversion.yaml <#37 (comment)> : > + - apiGroups: + - extensions + resources: + - ingresses + verbs: + - '*' + serviceAccountName: gitea-operator + strategy: deployment + installModes: + - supported: true + type: OwnNamespace + - supported: true + type: SingleNamespace + - supported: false + type: MultiNamespace + - supported: true Should this be false? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37?email_source=notifications&email_token=AAA5JFN4YYV7JH5Q6C5C543REPUA7A5CNFSM4KRQYOZKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCWVHFPQ#pullrequestreview-363492030>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5JFMBY4B6F7NAF745JZDREPUA7ANCNFSM4KRQYOZA> .