chore(installation): remove non-OLM installation doc; add link to OLM quickstart (RHIDP-2707) (RHIDP-3497)

[nickboldt]

What does this PR do?

chore(installation): remove doc about non-OLM installation method; add extra link to OLM quickstart at https://olm.operatorframework.io/docs/getting-started/ (RHIDP-2707) (RHIDP-3497)

Signed-off-by: Nick Boldt [email protected]

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

• https://issues.redhat.com/browse/RHIDP-2707
• https://issues.redhat.com/browse/RHIDP-3497

How to test this PR?

N/A

PR Checklist

As the author of this Pull Request I made sure that:

• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Relevant user documentation updated
• Relevant contributing documentation updated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-700/ @ 12/02/24 16:06:43

[nickboldt]

/cherry-pick release-1.3
/cherry-pick 1.2.x

[openshift-cherrypick-robot]

@nickboldt: once the present PR merges, I will cherry-pick it on top of 1.2.x, release-1.3 in new PRs and assign them to you.

In response to this:

/cherry-pick release-1.3
/cherry-pick 1.2.x

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.

[rm3l]

I think we should also update the instructions for AKS: https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/installing_red_hat_developer_hub_on_microsoft_azure_kubernetes_service/proc-rhdh-deploy-aks-operator_title-install-rhdh-aks#proc-rhdh-deploy-aks-operator_title-install-rhdh-aks

Right now, the first step in this procedure is Obtain the Red Hat Developer Hub Operator manifest file, named rhdh-operator-<VERSION>.yaml [...] (with no information on how to obtain that manifest), then Apply the modified Operator manifest to your Kubernetes cluster. There is no mention of OLM there.

But the instructions to install the Operator with OLM should be quite similar on AKS and EKS (not sure if the last step on changing the Service Type to NodePort is needed on AKS).

cc @gazarenkov

[rm3l]

/hold

[rm3l]

I think we should also update the instructions for AKS: docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/installing_red_hat_developer_hub_on_microsoft_azure_kubernetes_service/proc-rhdh-deploy-aks-operator_title-install-rhdh-aks#proc-rhdh-deploy-aks-operator_title-install-rhdh-aks

Right now, the first step in this procedure is Obtain the Red Hat Developer Hub Operator manifest file, named rhdh-operator-<VERSION>.yaml [...] (with no information on how to obtain that manifest), then Apply the modified Operator manifest to your Kubernetes cluster. There is no mention of OLM there.

But the instructions to install the Operator with OLM should be quite similar on AKS and EKS (not sure if the last step on changing the Service Type to NodePort is needed on AKS).

As discussed, this can be updated in a follow-up PR to avoid blocking this one.

/unhold
/lgtm

cc @nickboldt

[rm3l]

I think we should also update the instructions for AKS: docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/installing_red_hat_developer_hub_on_microsoft_azure_kubernetes_service/proc-rhdh-deploy-aks-operator_title-install-rhdh-aks#proc-rhdh-deploy-aks-operator_title-install-rhdh-aks
Right now, the first step in this procedure is Obtain the Red Hat Developer Hub Operator manifest file, named rhdh-operator-<VERSION>.yaml [...] (with no information on how to obtain that manifest), then Apply the modified Operator manifest to your Kubernetes cluster. There is no mention of OLM there.
But the instructions to install the Operator with OLM should be quite similar on AKS and EKS (not sure if the last step on changing the Service Type to NodePort is needed on AKS).

FYI, I've created a follow-up JIRA to capture this: https://issues.redhat.com/browse/RHIDP-5032
I tried to update the instructions for AKS to require OLM. But since the OLM steps are quite similar, I think it might be worth refactoring and sharing the same OLM-related content for AKS and EKS, to avoid having a lot of duplicate content.

@hmanwani-rh @nickboldt Here is a quick draft PR (building on top of this one): #729
LMK if it makes sense. If not, no problem to close it, and let the docs team work on https://issues.redhat.com/browse/RHIDP-5032 later.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[themr0c]

/cherry-pick release-1.4

[openshift-cherrypick-robot]

@nickboldt: new pull request created: #777

In response to this:

/cherry-pick release-1.3
/cherry-pick 1.2.x

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.

[openshift-cherrypick-robot]

@themr0c: new pull request created: #778

In response to this:

/cherry-pick release-1.4

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.

[openshift-cherrypick-robot]

@nickboldt: new pull request created: #779

In response to this:

/cherry-pick release-1.3
/cherry-pick 1.2.x

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.