Configure Helm

This section provides information to configure Helm.

About this task

To configure Helm do the following:

Procedure

  1. Change to the helm directory and edit the global configuration
    Configure the values.yaml file with specifics for your deployment. The following are some important fields, their description, and default values where applicable:
    • serverHostname

      This should be defined as the fully-qualified-host-name of the system as you would expect users to access via a web browser. Default is meetings.company.com

    • jwtCookieDomain

      This should be defined as the domain part of the fully-qualified-host-name. It is used for single-sign-on with the Sametime Proxy deployment. For example, if the proxy is webchat.company.com and the meeting server is meetings.company.com then the cookie domain should be company.com so that cookies can be shared between the two deployments. Default is empty, meaning no SSO is configured.

    • sametimeProxyHost

      This is the resolvable name or IP address of the Sametime Proxy v11.6 host. Default is empty.

    • sametimeProxyPort

      This is the port of the Sametime Proxy v11.6 host. Default is 443.

    • idpUrl

      If SAML is used for authentication, this is the IDP URL defined in that configuration. Default is empty.

    • jvbPort

      This is the media port used by the deployment. This defines the Kubernetes NodePort which will be used in the deployment. The value must be in the range of 30000-32767 unless you have specialized the node port range configuration. Default is 30000.

    • privateIp

      This is the network address by which your server will be accessed.

    • numberOfRecorders

      This is the fixed number of recorders and limits the number of meetings which may be recorded at one time for a given static deployment. This value should match the number of virtual sound devices you have configured on the host.

      If you deploy on a cloud provider, this is the default number of recorders which should match your minimum number of nodes in the recorder node group assuming a 1-to-1 configuration of pod-to-node. The number of recorder nodes will grow from this minimum, as needed, up to the maximum size of the recorder node group. Default is 5.

    • recordingsExpireInDays

      These are the number of days a meeting recording will be available for download/playback. Default is 3.

    • recordingsClaim

      This is the name of the persistent volume claim that defines the storage volume for meeting recordings. Default is sametime-meetings.

    • imageRepo

      This is the docker repository where the Sametime Meeting docker images are located. If you use a cloud provider image registry or your own private registry, you should update this setting to the base name of that image registry. Default is sametime-docker-prod.cwp.pnp-hcl.com and assumes that you have executed the ./load.sh script with its default configuration on each kubernetes node.

  2. Deploy the helm chart 
    helm install sametime-meetings .
    Note:
    • The command assumes you are in the helm directory. The . represents current directory.
    • Instead of sametime-meetings you can choose any descriptive name for the deployment. You can also deploy the application in a namespace via the -n or --namespace option. First create the namespace via kubectl create namespace.