[RHIDP-5032] Add procedure for deploying the Operator on AKS using OLM

[rm3l]

#700 clarified that the Operator installation requires OLM. As such, it removed the non-OLM steps for deploying the operator on EKS.

As raised in #700 (review), this PR updates the instructions for AKS accordingly by adding the missing OLM steps for 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. See 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

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):

• 1.4
• 1.3

Add the relevant labels to the Pull Request.

Issue:
https://issues.redhat.com/browse/RHIDP-5032

Preview:

• https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-729/install-rhdh-aks/
• https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-729/install-rhdh-eks/

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-729/ @ 01/04/25 22:02:43

[themr0c]

To respect modular docs templates, and for minimalism:

Suggested change

	.Additonal resources
	* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.
	.Prerequisites
	* You installed the Operator Lifecycle Manager (OLM) framework. See link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)].

[themr0c]

Or it seems, leftovers? (present at line 22)

Suggested change

	.Additonal resources
	* For information about the OLM, see link:https://olm.operatorframework.io/docs/[Operator Lifecycle Manager(OLM)] documentation.

[rm3l]

Based on your feedback, I've updated this and removed the leftovers:

[rm3l]

@themr0c Thanks for reviewing this. I've updated the PR based on your feedback. PTAL.

PS: Since this PR is based on #700, I think we can probably close #700. This way, this PR would fix both https://issues.redhat.com/browse/RHIDP-2707 and https://issues.redhat.com/browse/RHIDP-5032. Or you can merge #700 first and I'll rebase this one. Up to you ;-)

[rm3l]

BTW, any idea why the text preview on https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-729/install-rhdh-aks/#proc-rhdh-deploy-aks-operator_title-install-rhdh-aks is in italic?
I thought it was an issue in this PR, but it also happens on the main branch - see https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/main/admin-rhdh/

Is that expected?

[rm3l]

/cherry-pick release-1.3

[openshift-cherrypick-robot]

@rm3l: 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.

[linfraze]

Thank you for the content!

[rm3l]

Welcome back and thanks for the review, @linfraze !! I've incorporated your suggestions. PTAL. Thanks.

[rm3l]

/assign @linfraze

[linfraze]

@rm3l thanks for the updates! I did catch a couple other things - a minor attribute replacement but also something more major:

We need to take a look at the Installing the Red Hat Developer Hub Operator procedure to see if it can be reused in this procedure as-is. We want to single-source whenever possible. Regardless of whether the existing procedure can go straight in here or needs to be rewritten, we need to insert a separate procedure module rather than insert the procedure for installing the Operator as a sub-heading within the procedure for Deploying on AKS at Line 9 -- We would ideally want to structure this procedure to be consistent with how the Installing RHDH on OCP doc is structured. We can chat about this in the next Install WG meeting, too, if needed.

[linfraze]

Suggested change

	. Create an Image Pull Secret named `rhdh-pull-secret` using your Red Hat credentials to access images from the protected `registry.redhat.io` as shown in the following example:
	. Create an Image Pull Secret named `rhdh-pull-secret` using your {companyname} credentials to access images from the protected `registry.redhat.io` as shown in the following example:

replace company / product names with attribute

[linfraze]

We already have a separate procedure module for this that is applicable to OCP, EKS, and AKS but is currently only used in the OCP doc. We need to insert it here with metadata rather than rewrite it here this way.

See Installing the Red Hat Developer Hub Operator for example

I will also locate and find the proc file that needs to be inserted / reviewed. If it turns out that the existing file cannot be reused as-is, we must address that.

[linfraze]

proc-install-operator is the file that needs to be inserted with includes metadata.

@rm3l can you please review it and let me know if there is anything that needs to be updated for AKS or if it can be used as-is?

https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/main/modules/installation/proc-install-operator.adoc