Configuring Ingress for Mux

Before you begin

Complete the steps in the topic Installing Ingress. It is recommended to save the file that you are creating as a result of this topic. Do not save the file in the helm folder; save it at the root directory or sub-directory where the Sametime installation package was unzipped.

About this task

Sametime mux serves connections from Sametime Connect and embedded clients on port 1533. This connection can be routed through the ingress controller as well. This is suitable for an on-premise Kubernetes cluster.

If you are deploying in a cloud hosted Kubernetes environment (Google Kubernetes Engine, Amazon Elastic Kubernetes Service, etc) the Sametime mux is deployed as a Kubernetes load balancer service automatically. These steps are not necessary for cloud hosted environments.

Procedure

  1. For traffic to flow through the Ingress controller, you must apply a configuration map to Ingress.
    Create a file called mux-configmap.yaml with the following content.
    
apiVersion: v1
kind: ConfigMap
metadata:
   name: tcp-services
   namespace: namespace_name
data:
   1533: "default/mux:mux"
    If ingress is installed in a namespace, include the namespace: namespace_name statement, otherwise remove it.
  2. Apply the configMap values to the configuration by running the following command. 
    kubectl apply -f mux-configmap.yaml
  3. Run the following kubectl patch command so that port 1533 is available. 
    kubectl -n ingress-nginx patch deployment ingress-nginx-controller --type=json -p='[\{"op": "replace", "path": "/spec/template/spec/containers/0/args", "value": ["/nginx-ingress-controller","--publish-service=$(POD_NAMESPACE)/ingress-nginx-controller","--election-id=ingress-controller-leader","--controller-class=k8s.io/ingress-nginx","--configmap=$(POD_NAMESPACE)/ingress-nginx-controller","--tcp-services-configmap=$(POD_NAMESPACE)/tcp-services"] }]'

What to do next

Verify the service. For more information, see Testing Sametime chat and meeting clients.