Hosting client files for Sametime on Kubernetes
Sametime clients can be configured by administrators using a managed-settings.xml or managed-community-configs.xml file which is hosted by a web server. Additionally, the Sametime client can be pre-configured with settings such as the host name and port. The client package can be hosted on a web server for download.
Ensure that you have access to kubectl command line tool.
Note: If Sametime is deployed in a namespace, append the -n namespace
argument to all kubectl commands.
This procedure copies the file from the machine that runs kubectl to the persistent volume and have the web pod automatically retrieve the file when it starts. Use this procedure for each file that you would host in the default downloads directory.
-
Place the file that you are making available to users on the machine that runs kubectl. Then change directories to where the files are located.
-
Run the following command to get the name of the web pod.
kubectl get pods
-
Run the following command to copy the file from the machine that runs kubectl to the web pod.
kubectl cp filename pod:/usr/share/nginx/downloads/.
- Where filename is the name of the file you are copying
-
Where pod is the web pod name For example, suppose the following for the variables:
-
The file name is managed-settings.xml
- The web pod name is
web-6d4cc59bc9-v8gf4
Then the command should be:
kubectl cp managed-settings.xml web-6d4cc59bc9-v8gf4:/usr/share/nginx/downloads/.
Note: If using a namespace, add the
-n namespace
argument afterkubectl
and beforecp
. -
Scale the web pod to 0, then up to 1.
kubectl scale deploy/web --replicas=0 kubectl scale deploy/web --replicas=1
-
Confirm the URL is working for download. Open a browser and enter the HTTPS formatted URL:
https://sametime.example.com/downloads/managed-settings.xml
- Where
sametime.example.com
is the host name of the Sametime server - Where managed-settings.xml is the name of the file being hosted
- Where
-
Hosting files containing the same file name
This topic covers the additional steps necessary for environments that require hosting multiple managed-settings.xml or managed-community-configs.xml files.
Parent Topic: Defining preferences in the managed-settings.xml file