Preparing your cluster
Prepare your cluster for the installation of Netcool® Operations Insight® on Red Hat® OpenShift®.
Follow the steps in the table to prepare your cluster.
Step | Action |
---|---|
1 | Provision the required machines. The hardware architecture on which Netcool Operations Insight is installed must be with x86 based architecture, like AMD64 and Intel. Kubernetes can have a mixture of worker nodes. For operating system and other detailed system requirements, search for the latest version of the Netcool Operations Insight product in the Software Product Compatibility Reports website: https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html |
2 | Download and install Red Hat OpenShift. Netcool Operations Insight must be installed by a user with administrative access on the cluster, so ensure that you have access to an administrator account on the target Red Hat OpenShift cluster. For Red Hat OpenShift documentation, see https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/
For Red Hat OpenShift videos, see: https://www.youtube.com/user/rhopenshift/videos Install the OpenShift command line interface
( |
3 | Create a custom namespace to deploy into.
Where
namespace is the name of the custom namespace that you want to
create.Optional: If you want multiple independent installations of Netcool Operations Insight within the cluster, then create multiple namespaces within your cluster. Run each installation in a separate namespace. Additional disk space and worker nodes are required to support multiple installations. |
4 | Create a docker registry secret to enable your deployment to pull Netcool Operations Insight images from
the IBM® Entitled Registry.
Note: This step assumes that the cluster has internet access to:
cp.icr.io , which
is IBM's Entitled Registry. An exemption is typically made
available for this along with other registries. If a
connection to these registries is not permitted due to security constraints, then a production grade
Docker 2 compatible image registry must be provided and an airgap installation performed to mirror
the external image registries internally. For more information, see Installing Netcool Operations Insight in an air-gapped environment (offline) with a bastion host for a full cloud install, or Installing cloud native Netcool Operations Insight components in an air-gapped environment (offline) with a bastion host for a hybrid install. |
5 | Ensure that your Red Hat
OpenShift environment is updated to allow
network policies to function correctly. In some Red Hat OpenShift environments an additional configuration is required to allow external traffic to reach the routes. This is due to the required addition of network policies to secure pod communication traffic. For example, if you are attempting to access a route which returns a 503 Application Not Availableerror, then a network policy may be blocking the traffic. Check if the ingresscontroller is
configured with the endpointPublishingStrategy: HostNetwork value by running the
command
If
endpointPublishingStrategy.type is set to HostNetwork , then the
network policy will not work against routes unless the default namespace contains the selector
label. To allow traffic, add a label to the default namespace by running the
command: For
more information, see https://docs.openshift.com/container-platform/4.8/networking/network_policy/about-network-policy.html
|
6 | (Optional) You can restrict the Netcool Operations Insight pods in a
namespace to only run on worker nodes with a specific tag. You can tag worker nodes by adding the
tag env=test or app=noi . For example, you can run the
command: and then edit the YAML on the
Netcool Operations Insight
namespace by adding the node-selector to the annotations section.
You can run the following command to edit the
YAML: The result
is:
|
7 |
|