Customizing business cards in Kubernetes

You can override the default business cards configuration by creating an extra-community-configs secret to hold the configuration files.

Kubectl commands are used to pull the existing file from the community pod to your local machine. You modify these files locally with the required settings, then create the secret containing the files.

The following procedures describes the steps to create a new secret. The example used in the steps shows creating a secret called extra-community-configs which overrides the values.yaml settings for LDAP. The extra-community-configs secret contains a copy of the configuration files used by the Community pod. For more information on secrets, see Managing secrets in Kubernetes.

Create a directory on your machine called extra-community-config at the root of where the Sametime installation package was decompressed.
```
mkdir extra-community-config
```
Use the cd command to change to the extra-community-config directory.
```
cd extra-community-config
```
Find the community pod name by running the get pods command.

The pod name has some hashes in it, for example: community-77d4695988-2bzrx): kubectl get pods.
Run the following command to pull a copy of the StCommunityConfig.xml file from the community pod specifying the name of the pod.
```
kubectl exec -it pod\_name --container community -- cat /local/notesdata/StCommunityConfig.xml >./StCommunityConfig.xml
```
This file must be available. No changes to it are needed at this time.
Run the following command to pull a copy of the UserInfoConfig.xml file from the community pod specifying the name of the pod.
```
kubectl exec -it pod\_name --container community -- cat /local/notesdata/UserInfoConfig.xml >./UserInfoConfig.xml
```
Using a text editor, open the local copy of the UserInfoConfig.xml file in edit mode. Modify the file as needed.

When finish, save and close the file.
Ensure that you are in the extra-community-config directory that was created earlier. Run the following command to create the secret. If you have a namespace dedicated to Sametime, add the -n argument with your namespace to ensure it is created in the correct namespace.
```
kubectl create secret generic extra-community-config --from-file=./ 
```
Use the cd command to change to the helm directory where the Sametime installation package was decompressed.
```
cd helm
```
Open the values.yaml file and put in edit mode.
Add the following line to the values.yaml file.
```
overrideCommunityConfigSecret: extra-community-config
```
When finished save and close the file..
Apply your changes to the environment.

Verify that you are in the helm directory and run the following command to apply changes. Specify the Sametime deployment name for your environment. The default for Sametime Premium version 12 is sametime.
```
helm upgrade sametime\_deployment\_name .
```
Note: Be sure to include the dot at the end. It is part of the command.

If you are unsure of your deployment name, issue the helm list command to find the name. If you upgraded from an earlier Sametime release, the default name is sametime-meetings.
Restart the pods with the changes. Use the kubectl scale command to scale the pods to zero and then to one that have been changed. You must run the commands for each pod that the change affects.
1. Run the following command to scale the pod to zero.
  
  Scale the pod to zero, where pod_deployment_name is the pod name.
```
kubectl scale deploy pod\_deployment\_name --replicas=0
```
2. Run the following command to scale the pod to one.
```
kubectl scale deploy pod\_deployment\_name --replicas=1
```

Parent Topic: Setting up business cards