Refactor installation documentation

[geriom]

Changes

• Simplify installation instructions
• Move configuration docs to a separate file.
• Include vendor specific docs for OpenShift and Google Cloud.

As discussed in the proposal for this change during the community meeting, the documentation is only rendered correctly on the website. This and the corresponding PR on the website repo must be merged in short succession.

Previews

• Pipelines installation
• Post-installation configurations
• Registry authentication

/kind documentation

Submitter Checklist

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

• Has Docs included if any changes are user facing
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• 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
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[bendory]

Forgive my ignorance if this is a newbie question... is there a staging area where I can see the rendered website as it will appear after the merge?

[lbernick]

Thanks Geri! I really like the tabs for installing on different providers/with different registries!

[geriom]

Forgive my ignorance if this is a newbie question... is there a staging area where I can see the rendered website as it will appear after the merge?

@bendory The links in the "Preview" section take you there. For changes outside the website repo the preview is not autogenerated, I created a separate PR just to generate the preview.

[bendory]

Forgive my ignorance if this is a newbie question... is there a staging area where I can see the rendered website as it will appear after the merge?

@bendory The links in the "Preview" section take you there. For changes outside the website repo the preview is not autogenerated, I created a separate PR just to generate the preview.

OIC, thank you -- these look great, I love the way you can now "choose your own adventure!"

/LGTM

[tekton-robot]

@bendory: changing LGTM is restricted to collaborators

In response to this:

Forgive my ignorance if this is a newbie question... is there a staging area where I can see the rendered website as it will appear after the merge?

@bendory The links in the "Preview" section take you there. For changes outside the website repo the preview is not autogenerated, I created a separate PR just to generate the preview.

OIC, thank you -- these look great, I love the way you can now "choose your own adventure!"

/LGTM

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.

[geriom]

/retest

[jerop]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerop, lbernick

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 [jerop,lbernick]

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

[jerop]

/retest

[afrittoli]

Thanks for this @geriom !
A couple of questions:

• we have no way to see here the final rendering result of this PR. Would it make sense to have a PR against the website repo that pulls in this PR and shows the final result?
• I like that we have tabs with different installation options. Should we have one about using the operator that points to the operator docs as well?
• NIT: I'm not entirely sure about the "post-install" naming. The configuration is not exclusively done after the installation, the installation files can also be customised to install directly with the required configuration

[geriom]

@afrittoli

• we have no way to see here the final rendering result of this PR. Would it make sense to have a PR against the website repo that pulls in this PR and shows the final result?

I was thinking the same thing. For this PR I rendered it locally see preview here, but that's not a feasible solution long term. Not sure how much engineering that would require, but it's probably worth the effort. I opened an issue on the website repo to track this

• I like that we have tabs with different installation options. Should we have one about using the operator that points to the operator docs as well?

Yes, I think that's a good idea. We can make that a separate issue and iterate this doc? since this PR is been open for two moths now.

• NIT: I'm not entirely sure about the "post-install" naming. The configuration is not exclusively done after the installation, the installation files can also be customized to install directly with the required configuration.

Renamed the file to additional-configs.md and changed the title to "Additional configuration options", what do you think?

[afrittoli]

Thanks for the updates!
/lgtm