[TEP-0129] Move CRDs definition and update multi-tenancy docs accordingly

[afrittoli]

Changes

Move CRD files into the 300-crds folder to make it easier to not install CRDs in case of multi install into a single cluster. Since the release pipeline uses ko -R, this doesn't change anything for now in the release files.

Update the multi-tenancy documentation to include all aspects of multi-tenancy and explain how to install the CRDs separately from the new dedicated folder.

Signed-off-by: Andrea Frittoli [email protected]

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• [x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• [x] Has Tests included if any functionality added or changed
• [x] Follows the commit message standard
• [x] Meets the Tekton contributor standards (including functionality, content, code)
• [x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• [x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• [x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Document simple installation instructions for a Tekton multi-tenancy setup.

/kind documentation

[afrittoli]

Do we need to update some scripts or docs with an -R (recursive) ?

The -R is already needed because of the namespace, but I'll doublecheck to be sure

[afrittoli]

/test pull-tekton-pipeline-alpha-integration-tests

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [vdemeester]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[afrittoli]

@dibyom would you be interested in reviewing this, since you reviewed #923 previously?

[chitrangpatel]

/lgtm