Configure high capacity for chat

Sametime supports up to 10,000 simultaneous log-ins with a standard single community pod, mux pod, and proxy pod in a Kubernetes deployment. Docker deployments of Sametime support 10,000 simultaneous log-ins.

The Sametime mux is used for front-end client connections between the Sametime Connect client and the Sametime Embedded client inside of HCL Notes. If you need additional capacity for these clients, you can deploy multiple community pods inside your Kubernetes cluster. The number of community pods is defined in the values.yaml file, and each additional pod supports up to 10,000 additional clients. The community pod does not axiomatically scale. It is important to estimate the number of pods needed and define the setting in the values.yaml file.

When changing

In the values.yaml file, ensure that this setting is set to true, which is the default setting:
```
enableMuxDeployment: true
```
Change the below setting to the desired number of community pods:
```
numberOfCommunityServers: 1 
```
To find the Kubernetes service that front-ends the mux issue the command:
```
 kubectl get svc | grep mux 
```
The ingress controller in a Kubernetes cluster front-ends the connection to the web and mobile clients and the proxy pod services those connections. Additionally, the community pod validates log ins and service the users as well. Sametime supports up to 10,000 simultaneous connections in a Kubernetes environment, and if more are needed deploy an additional 1 ingress controller pod, 1 proxy pod, and 1 community pod per 10,000 web and mobile clients.
Apply your changes to the environment run the helm uninstall command and after it completes, run the helm install command.

If you are not changing the value from or to a value=1, run the helm upgrade command to apply the changes.

Parent Topic: Clustering and high availability