Configuring the Kubernetes Cluster

After you install the CDF Installer, complete the following steps to configure the cluster.

  1. Use your remote desktop to access the jumphost.
  2. Browse to the cluster using your private DNS address at port 3000.
  3. For example:

    https://installer.private.arcsight.com:3000
  4. Log in using admin (user ID) and the password you specified during the CDF installation.
  5. The system prompts you to upload the following ArcSight installer metadata.tar file:

    arcsight-installer-metadata-<version>.xx.tar
  6. On the Security Risk and Governance - Container Installer page:
    1. Select the CDF base product metadata version.
    2. To continue, click Next.
  7. On the End User License Agreement page:
    1. Review the End User License Agreement.
    2. To accept the agreement, select the I agree… check box.
    3. (Optional) To have information passed to Micro Focus, select the I authorize... check box.
    4. To continue, click Next.
  8. On the Capabilities page:
    1. Select the capabilities and products you want to install.
    2. For example, to install Transformation Hub as a standalone install, select the Transformation Hub check box.

      Other products might require Transformation Hub or other capabilities as prerequisites. Such requirements will be noted in the pull-down text associated with the capability.
    3. To show additional information associated with the product, click the > (greater than) arrow.
    4. To continue, click Next.
  9. On the Database page:
    1. Ensure the PostgreSQL High Availability box is clear. This database is not used by capabilities in SODP.
    2. To continue, click Next.
  10. On the Deployment Size page:
    1. Based on your planned implementation, select a size for your deployment.
    2. Additional nodes, with each running on their own host system, can be configured in subsequent steps.

      The installation will not proceed until the minimal hardware requirements for the deployment are met.
      SizeMinimum Worker NodesCoresMemoryDisk
      Small Cluster1 Worker Node4 Cores16 GB50 GB
      Medium Cluster1 Worker Node8 Cores32 GB100 GB
      Large Cluster3 Worker Nodes16 Cores65 GB256 GB

    3. To continue, click Next.
  11. On the Connection page:
    1. In the External Hostname field, the system populates an external hostname automatically from either:
      • The Virtual IP (VIP) specified earlier during the install of CDF (--ha-virtual-ip parameter)

      • The master node hostname if the --ha-virtual-ip parameter was not specified during CDF installation
    2. Confirm the port is correct.
    3. To continue, click Next.
  12. On the File Storage page, for each NFS volume to configure:
    1. In the File System Type drop-down, ensure Self-hosted NFS is selected. Self-hosted NFS refers to the NFS server that you prepared earlier.
    2. In File Server field, enter the IP address or FQDN for the NFS server.
    3. In the Exported Path drop-down, select the appropriate volume. (If using NetApp, enter the path manually instead; for example, /nfs/arcsight-volume, /nfs/db-backup-vol, /nfs/db-single-vol, /nfs/itom-logging-vol itom-vol.)
    4. Click Validate. All volumes must validate successfully to continue with the installation.
    5. The following volumes must be available on your NFS server.

      CDF NFS Volume Claim

      Your NFS volume

      itom-vol

      <NFS_ROOT_FOLDER>/itom_vol

      db-single-vol

      <NFS_ROOT_FOLDER>/db-single-vol

      db-backup-vol

      db-backup-vol | <NFS_ROOT_FOLDER>/db-backup-vol

      itom-logging-vol

      <NFS_ROOT_FOLDER>/itom-logging-vol

      arcsight-volume

      <NFS_ROOT_FOLDER>/arcsight-volume

    6. To continue, click Next.
    7. After you click Next, the infrastructure implementation will be deployed. Please ensure that your infrastructure choices are adequate to your needs. An incorrect or insufficient configuration might require a reinstall of all capabilities.

  13. On the Confirm dialog, to start deploying nodes, click Yes.
  14. Once all Nodes have been configured, and all services have been started on all nodes, the Preparation Complete page displays.

    This message means the installation process is now ready to configure product-specific installation attributes.

  15. To configure the products and components of the deployment, click Next.
If the installation of the products seems to stall, check the logs for this message:

mkdir: cannot create directory 'data/pg-data-backup/log': Permission denied

If this message is found, you will need to manually reassign the NetApp volumes permissions by running these commands:
cd  <NFS_ROOT_FOLDER>
chown -R 1999:1999 itom-vol
After the permissions have been reassigned, the itom-pg-backup pod will start running and the suite deployment will finish successfully.