manifest files for easy prototyping

[rahulanand16nov]

This PR tries to address Issue #16 to provide manifest files for situations where cloning the whole operator repo is not necessary.

[rahulanand16nov]

There was one typo in kustomization.yaml file which was failing deployment manifest but I hope its fixed now.

[rahulanand16nov]

Weird, the last run was two tests failing and now only one, but I am passing all the tests locally? Flaky tests?

[mikenairn]

Is there no way to use the manifests already generated for the bundle? https://github.com/Kuadrant/limitador-operator/tree/main/bundle/manifests I'm not sure everything (Roles/RoleBindlings) is included though ...

If you are generating file(s) that need to be committed, you might want to consider adding a CI job to ensure they are always regenerated correctly before allowing changes to be merged https://github.com/Kuadrant/kuadrant-operator/blob/main/.github/workflows/test.yaml#L109 https://github.com/Kuadrant/kuadrant-operator/blob/main/make/verify.mk

[rahulanand16nov]

Is there no way to use the manifests already generated for the bundle? https://github.com/Kuadrant/limitador-operator/tree/main/bundle/manifests I'm not sure everything (Roles/RoleBindlings) is included though ...

I guess the requirement was to have a single document but I am not sure... @guicassolato any thoughts?

Edit: Good idea to verify generated manifests. 🤔

[guicassolato]

I guess the requirement was to have a single document but I am not sure... @guicassolato any thoughts?

Suggestion was indeed motivated by the desire to install and deploy the operator from one single YAML file, like option provided by https://github.com/kuadrant/authorino-operator.

With OLM, theoretically we could list all the steps (or have a tool) to automate: downloading the CSV bundle, applying the manifests, creating catalog source, subscription, etc. However, I don't see that being much simpler for the command-line than git clone ... && make install deploy. I wanted to avoid too may steps and having to download operator files locally.

In the Authorino docs, we have user guides such as this one, where Limitador is deployed and a rate limit config defined, all without support from the operator. I would like to enhance that one step into:

1. Deploy the Limitador Operator
2. Create a Limitador CR
3. Create a RateLimit CR

More explicit, yet with minimum number of commands for the user to follow.

Edit: Good idea to verify generated manifests. 🤔

+1 to that.

[rahulanand16nov]

@mikenairn added a verifying script which gets executed in the CI. Please merge if looks good to you.

[mikenairn]

/lgtm