Home

Install WebSphere Liberty Operator Development driver (for testing and demo purposes only)

Note: This driver is for testing and demo purposes only. Use the instructions at https://ibm.biz/wlo-docs for installing production-ready versions of WebSphere Liberty Operator that are available from the IBM Operators Catalog.

1. Update your OpenShift cluster with a global pull secret for the cp.stg.icr.io entitled registry:

• Get an entitlement key to the IBM Entitled Container Fulfillment Registry. Log in to MyIBM Container Software Library with the IBMid and password that are associated with the entitled software. Click on 'Container software library' on the left and expand the listed item. It should show that you have entitlement for 'all' IBM software. If you are not able to access the library or you don't have entitlement to 'all' IBM software then follow the process under Obtaining a staging entitlement key .
• In the Entitlement keys section, pick an existing key or generate a new key. Select Copy key to copy the entitlement key to the clipboard.
• Use the OpenShift cluster UI to configure the global pull secret with entitled registry (cp.stg.icr.io) credentials.
• In the OpenShift cluster UI, click Workloads > Secrets and select the openshift-config namespace.
• Find the existing pull-secret secret.
• Select Edit Secret.
• Click Add Credentials to add an entry for the entitled registry. Specify cp.stg.icr.io as the registry server address, cp as the username, and the entitlement key that you obtained in the previous step as the password.

Note: CatalogSource based install option is not available yet for 1.6.2 release candidate due to the wider infrastructure related issue. When it's available, we'll add the details here and notify.

2. Install options:

• To install the Operator using kubectl, use the artifacts in https://github.com/WASdev/websphere-liberty-operator/tree/deploy-1.6.2/internal/deploy/kubectl
• To install the Operator using kustomize, use the artifacts in https://github.com/WASdev/websphere-liberty-operator/tree/deploy-1.6.2/internal/deploy/kustomize/daily

4. Create custom resources (CRs) to deploy applications and to gather trace, dump and performance data:

• Sample CRs are available from the OpenShift UI as well as in this folder
• Configuration options within the CRs are the same as Open Liberty Operator.

Follow the documentation at https://www.ibm.com/docs/en/was-liberty/base?topic=operator-using-websphere-liberty

---

New features in 1.6.2

Note: Known issues with the pre-release driver are listed at the bottom. Please review them before opening new issues.

Priority Class

Support for specifying priority class for application pods is added in WLO 1.6.2.

Create a PriorityClass as an administrator. Example: https://github.com/application-stacks/runtime-component-operator/blob/main/examples/priorityclass/01-priorityclass.yaml

Then, set the priority class in CR. Example:

spec:
  applicationImage: APP_IMAGE
  priorityClassName: service-critical

For more information on pod priority, refer to Kubernetes documentation.

Known issues