Skip to content

Commit 2670fff

Browse files
authored
Merge pull request #45 from IBM/update_merlin_install
update the doc about merlin v2 installation
2 parents 0664449 + 28517d2 commit 2670fff

File tree

1 file changed

+10
-48
lines changed

1 file changed

+10
-48
lines changed

docs/guides/platform/Install_MERLIN_Online.md

+10-48
Original file line numberDiff line numberDiff line change
@@ -36,28 +36,6 @@ Install the OpenShift command line interface (oc) on the cluster's boot node and
3636

3737
The storage configuration must satisfy the sizing requirements. For more information on the storage classes that are needed for installing IBM i Modernization Engine For Lifecycle Integration, see [Configure a default storage class](./guides/platform/Data_Storage_for_MERLIN.md).
3838

39-
## Create a custom project (namespace)
40-
41-
Create a project (namespace) to deploy IBM i Modernization Engine For Lifecycle Integration into.
42-
43-
A project is a Openshift namespace. a custom project (namespace) must be created and not use the default, kube-system, kube-public, openshift-node, openshift-infra, or openshift projects (namespaces). This is because IBM i Modernization Engine For Lifecycle Integration uses Security Context Constraints (SCC), and SCCs cannot be assigned to pods created in one of the default OpenShift projects (namespaces).
44-
45-
Create a project (namespace) with either of the following methods:
46-
47-
- Option 1: Create a project with the OpenShift console
48-
- Option 2: Create a project with the OpenShift CLI
49-
50-
### Option 1: Create a project with the OpenShift console
51-
52-
From the OpenShift console, click Home > Projects. Select Create Project, specify the Name of the project, for example **merlin** and click Create.
53-
54-
![Create Openshift Namespace](../../images/guides/createNamespaceOnOpenshift.png)
55-
56-
### Option 2: Create a project with the OpenShift CLI
57-
```
58-
Run oc create namespace <namespace> where <namespace> is the name of the project (namespace), for example **merlin**.
59-
```
60-
6139
## Create the entitlement key secret
6240

6341
Complete the following steps to create a docker-registry secret to enable the deployment to pull the IBM i Modernization Engine For Lifecycle Integration images from the IBM® Entitled Registry.
@@ -159,11 +137,11 @@ Install Merlin operator with either of the following installation methods:
159137
- Click the IBM i Modernization Engine for Lifecycle Integration tile. The IBM i Modernization Engine for Lifecycle Integration window is displayed.
160138
- Click Install. The Install Operator page is displayed.
161139
- Enter the following values:
162-
```
163-
* Set the Namespace to be the project (namespace) in which to install the Operator, such as **merlin**.
164-
* Set Update Channel to v2.0.
165-
* Set Approval Strategy to Automatic.
166-
```
140+
141+
* Set the Namespace to be `openshift-operators` in which to install the Operator.
142+
* Set Update Channel to v2.0.
143+
* Set Approval Strategy to Automatic.
144+
167145
- Click Install and wait for the Merlin operator to install.
168146
- Verify that the Merlin operator is successfully installed.
169147
- Navigate to Operators > Installed Operators, and select the project from the Projects dropdown. IBM i Modernization Engine for Lifecycle Integration and its dependant operator in the project are listed with a status of Succeeded.
@@ -175,30 +153,14 @@ Install Merlin operator with either of the following installation methods:
175153

176154
### Option 2: Install the operator with the OpenShift CLI
177155

178-
- Create Operator Group.
179-
180-
Create an Operator group in the custom project (namespace), or the Merlin operator will not install. There might be an Operator group for managing a namespace for given APIs. If there is an Operator group for the namespace, do not create a second one.
181-
182-
- Create the Operator group by running the following command:
183-
```
184-
cat << EOF | oc apply -f -
185-
apiVersion: operators.coreos.com/v1
186-
kind: OperatorGroup
187-
metadata:
188-
name: merlin-operator-group
189-
namespace: <namespace>
190-
EOF
191-
```
192-
Where <namespace> is the project (namespace created earlier in Create a custom project (namespace).
193-
194-
- Install the Merlin operator with the following command.
156+
Install the Merlin operator with the following command.
195157
```
196158
cat << EOF | oc apply -f -
197159
apiVersion: operators.coreos.com/v1alpha1
198160
kind: Subscription
199161
metadata:
200162
name: ibmi-merlin-operator
201-
namespace: <namespace>
163+
namespace: openshift-operators
202164
spec:
203165
channel: v2.0
204166
installPlanApproval: Automatic
@@ -207,13 +169,13 @@ spec:
207169
sourceNamespace: openshift-marketplace
208170
EOF
209171
```
210-
Where <namespace> is the project (namespace) created earlier, such as merlin.
211172

212173
After a few minutes, the operator is installed. Verify that the all components are in the Succeeded state by running the following command:
213174
```
214-
oc get csv -n <namespace> | grep ibmi-merlin-operator
175+
oc get csv -n openshift-operators | grep ibmi-merlin-operator
215176
```
216-
Where <namespace> is openshift-operators if using the AllNamespaces installation mode, or the project (namespace) created earlier in Create a custom project (namespace) if using the OwnNamespace installation mode. For more information about installation modes, see Operator installation mode.
177+
178+
> Note: Make sure the namespace/project for Merlin operator is `openshift-operators`.
217179
218180
## Deploy Merlin instance
219181
Once Merlin operator has been installed into a specific project, Merlin instance can be installed.

0 commit comments

Comments
 (0)