Prerequisite | Description |
---|---|
Prepare your IBM Cloud Kubernetes Service cluster. | Configure the cluster |
To install the server image using the Helm command-line client, install kubectl and then set up the Helm CLI (command line interface). | Install and set up kubectl Install and set up the Helm CLI |
The containerized server, like the on-premises version, requires a database. The database can be installed in any location that can be accessed by the cluster, such as an on-premise location or in a cluster. | Install database. Note: Unlike the on-premises version of
IBM UrbanCode Deploy, the containerized version does not support the Apache Derby database.
|
The installation material consists of an IBM Passport Advantage archive (PPA) file, that contains a Docker image and a Helm chart. Helm is the Kubernetes package management tool. Helm charts are packages similar to debs and rpms packages. Download the PPA file for your operating system from the IBM Passport Advantage website. PPA files are available for x86, Z Linux systems and PowerPC (LE). | Load PPA archive file |
Two persistent volumes are required for UrbanCode Deploy. One volume holds the
JDBC driver or drivers and the other contains the server's /appdata
directory. If your Kubernetes cluster does NOT support dynamic persistent volumes, you need to manually create and set up storage volumes in your cluster. Note: If your Kubernetes cluster
supports dynamic storage provisioning, this prerequisite is not required. Storage is automatically
managed.
|
Create persistent volumes |
Secret - A Kubernetes Secret object must be created to store the initial UrbanCode Deploy administrator password and the password used to access the database mentioned above. These passwords are retrieved during Helm chart installation. The secret must be named 'HelmReleaseName-secrets' where 'HelmReleaseName' is the release name you give when installing this Helm chart or you can create a secret with any name and pass the name as a Helm Chart parameter value. | The secret can be created either by using the Cluster Console or using the kubectl CLI.
Create a file named secret.yaml with the following contents, using your Helm Relese name and base64 encoded values.
Create the Secret using kubectl apply
Delete or shred the secret.yaml file. |
Copy the JDBC drivers to the extLib persistent volume created in your Kubernetes cluster. | Use a ConfigMap to copy the JDBC files into the persistent volume. This sample YAML file describes a ConfigMap resource with a shell script, named script.sh. The script performs a wget command to pull the MySQL.jar file from a web server and copy it to the ${UCD_HOME}/ext_lib/ directory in the container. In order for the image initialization code to find and execute the script, the script must be named script.sh.
To create your own ConfigMap, make a copy using the copy icon provided, place the content in a file called userscript.yaml and run the following command: kubectl apply -f user-script.yaml |
Access your containerized instance of IBM UrbanCode Deploy.