Preparing for installation of WebSphere Liberty operator
A cluster administrator prepares the environment before they WebSphere® Liberty operator.
Before you begin
Determine your deployment needs.
By default, the WebSphere Liberty operator uses the AllNamespaces installation mode. This installation mode supports single and multiple instances of WebSphere Liberty operator. For other installation modes, choose the namespace in which to install the operator. WebSphere Liberty operator supports installing multiple instances in the same cluster, but each instance must be in its own namespace.
Follow the instructions that apply to your installation configuration.
Completing prerequisites for an OpenShift cluster
- Ensure that your OpenShift cluster meets the system requirements. In particular, ensure that sufficient worker node capacity is available and that compatible persistent storage is installed.
- Create the catalog sources.
- Create the IBM® Operator catalog source.
Follow instructions in Adding the IBM operator catalog in the IBM Cloud Pak documentation to create a catalog source. A catalog entry is created in your Operator Hub.
- Verify the
CatalogSources
installation.- Check the
CatalogSources
operators.oc get catalogsource -n openshift-marketplace
The command output lists the installed operators for
CatalogSources
. Ensure theibm-operator-catalog
is listed.ibm-operator-catalog IBM Operator Catalog grpc IBM 1s
- Check that the pods for
CatalogSources
are running.oc get pods -n openshift-marketplace
You want the command output to show a
Running
status for the pods. Ensure theibm-operator-catalog
pod is listed and reachesRunning
status.NAME READY STATUS RESTARTS AGE ibm-operator-catalog-r96r2 1/1 Running 0 1s
- Check the
- Create the IBM® Operator catalog source.
Completing prerequisites for a non-OCP Kubernetes cluster with Operator Lifecycle Manager (OLM)
- Ensure that your Kubernetes cluster meets the system requirements. In particular, ensure that sufficient worker node capacity is available and that compatible persistent storage is installed.
- Create the catalog sources.
- Create the IBM Operator catalog source.Follow instructions in Adding the IBM operator catalog in the IBM Cloud Pak documentation to create a catalog source. A catalog entry is created in your Operator Hub.Note: Use
olm
as the value for the namespace parameter instead ofopenshift-marketplace
. - Verify the
CatalogSources
installation.- Check the
CatalogSources
operators.kubectl get catalogsource -n olm
The command output lists the installed operators for
CatalogSources
. Ensure theibm-operator-catalog
is listed.ibm-operator-catalog IBM Operator Catalog grpc IBM 1s
- Check that the pods for
CatalogSources
are running.kubectl get pods -n olm
You want the command output to show a
Running
status for the pods. Ensure theibm-operator-catalog
pod is listed and reachesRunning
status.NAME READY STATUS RESTARTS AGE ibm-operator-catalog-r96r2 1/1 Running 0 1s
- Check the
- Create the IBM Operator catalog source.
Completing prerequisites for a non-OCP Kubernetes cluster without OLM
- Ensure that your Kubernetes cluster meets the system requirements. In particular, ensure that sufficient worker node capacity is available and that compatible persistent storage is installed.
- Ensure that the
curl
andsed
programs are installed.
What to do next
Install the WebSphere Liberty operator with the OpenShift console, the OpenShift command-line interface (CLI), or the Kubernetes command-line interface.