1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Prerequisites for Deploying Siebel CRM on a Kubernetes Cluster

Prerequisites for Deploying Siebel CRM on a Kubernetes Cluster

This topic lists the prerequisites required to deploy Siebel CRM on a Kubernetes cluster using Siebel Installer for SCM.

This topic includes the following sections:

Prerequisites for Running Siebel Installer and Installing SCM

You'll need the following to successfully run Siebel Installer and install SCM:

  • Linux VM version 8 or above with minimum 20 GB free disk space.
  • Helm version 3.8 or later: A package that contains the resources needed to deploy an application on a Kubernetes cluster. The SCM Helm package contains the artifacts required to deploy Siebel on a Kubernetes cluster. It is also used to push the SCM package into the container registry and to deploy SCM and Siebel CRM on a Kubernetes cluster. For more information on installing Helm chart, refer the “Installing Helm” online documentation.
  • Podman: An open source tool for managing containers on Linux, Windows and so on. Here, Podman is used to mange the SCM container registry. For more information on installing Podman, refer the “Podman Installation Instructions” online documentation.
  • Kubectl: A command line tool that helps users to manage their Kubernetes clusters. Here, Kubectl is used to manage the cluster on which SCM and Siebel CRM are deployed.
  • VNC session or Xterm to run Siebel Installer in the GUI mode.
  • Container registry with the appropriate credentials: You must have an open container initiative compliant registry like Harbor with the following registry details:
    • Registry URL: The container registry URL.
    • Registry credentials: The user name and password to access the container registry.
    • (Optional) Registry prefix: When the prefix is specified, the repository path is constructed using the registry prefix. The registry user must have the privileges to create the repository or it must be created before running the installer.

Additional Prerequisite Resources for Installing SCM and Deploying Siebel CRM

You'll need the following additional resources to successfully install SCM and deploy Siebel CRM on a Kubernetes cluster using Helm:

  • Kubernetes cluster: A Kubernetes cluster to install SCM and Siebel CRM. You must configure access to the cluster in the Linux host, that is copy the kubeconfig file of the Kubernetes cluster to a directory on Linux and set the path of the environment variable KUBECONFIG as follows:
    export KUBECONFIG = "/scratch/.kube/<kubeConfigFile>"

    where <kubeConfigFile> is the configuration file of the Kubernetes cluster on which you want to install SCM and deploy Siebel CRM.

  • NFS share: You must create an NFS share to store the SCM and Siebel CRM environment state information. This directory should be accessible from the Kubernetes cluster worker nodes for mounting into the SCM pod and, later, into the Siebel CRM pods for the Siebel file system. For example:
    <nfsServerHost>:/<nfs-path>
    Note: The NFS share should have the no_root_squash parameter set for exports.
  • Kubernetes namespace: The logical division within the Kubernetes cluster in which you want to install SCM. You can create the namespace for SCM installation as follows:
    kubectl create namespace <namespace>

    where <namespace> is the name of the Kubernetes namespace to install SCM in.

    Note: You can also use an existing namespace, but ensure the namespace is empty.