Installation prerequisites
You must complete certain tasks before you install HCL DevOps Velocity (Velocity).
You must have completed the following tasks before you install Velocity on Kubernetes:
- Verified that your computer meets the hardware and software requirements. See System Requirements.
- Installed Red Hat OpenShift. For more information refer to OpenShift documentation.
- Installed Kubernetes on your computer. For more information refer to, Kubernetes documentation.
- Installed Helm on the Kubernetes cluster. See Installing Helm.
- Configured an OpenShift client instance.
- Installed an OpenShift command line interface (CLI) on the client instance.
- Obtained access to the PEM-format certificate and private key that you can use to configure OpenShift routes.
- Optional: Created a new
velocity-image-secret
. - Created a project in OpenShift. See Creation of a project.
- Installed the mandatory softwares. See Installation of mandatory softwares on Kubernetes cluster.
- Configured SSL certificate. See Configuration of custom Secure Sockets Layer (SSL) certificate.
Creation of a project
Ensure that you have created a project in the OpenShift.
Enter the following command in the OpenShift console to create a
project:
oc new-project <project_name> --description="<description>" --display-name="<display_name>"
Installation of mandatory softwares on Kubernetes cluster
Ensure that you have installed the following mandatory software:
- Installed MongoDB on the Kubernetes cluster. For more information, refer to
Bitnami documentation.Note: MongoDB is not bundled with the installation file, so you must install it separately.
- Installed the Ingress controller on the Kubernetes cluster. For more information refer to Bitnami documentation.
Configuration of custom Secure Sockets Layer (SSL) certificate
Ensure that you have configured a custom SSL certificate for the ingress controller external IP address or domain name to secure the data exchanged between browser and the Velocity application. For detailed instructions, see Configuring a custom Secure Sockets Layer (SSL) certificate.