Interaction with the deployment on a specific server

1. Type kubectl get pods -n mediakind | grep stream-processor. A list of pods appears with some information associated to each of them: name, ready, status, restarts, age.

2. Verify that the status is “Running” for all the pods. If this is not the case, the system may not behave as expected.

If any of the pods is not in “Running” state, type any or all of these commands to help you understand what is wrong:

• kubectl get pods -n mediakind: Get the status of all the pods running on the server. It may be that some other microservice is also not in “Running” state.
• kubectl describe pod -n mediakind <pod\_name\>: <pod_name> is the name of the pod that is not in “Running” state. Check the last part of the information. It can contain a list of warning or error events.

1. Type kubectl get pods -n mediakind | grep stream-processor. A list of pods appears with some information associated to each of them: name, ready, status, restarts, age.

   

   The installation of the stream-processor-asi and the stream-processor-simulcrypt controls is optional. They should not be present on your system unless you have chosen to install them and executed the additional installation steps as described in the installation guides.

2. Type kubectl logs -n mediakind <pod name> where <pod_name> is the name of the pod associated to the microservice of interest as it appears in the output of the previous command.

   • For most microservices, the output contains the logs for the (single) container running in the pod. For the mux pod, add -c mux to get the logs from Mux or to get the logs from PSI.
   • The output of the kubectl logs command can be easily used as input into less, grep, sed or other string/stream manipulation commands.
   • It is possible to also use the bark utility installed by default with the host application: kubectl logs -n mediakind <pod name>| bark to increase readability of the kubectl logs output.

1. Type kubectl get pods -n mediakind | grep stream-processor. A list of pods appears with some information associated to each of them: name, ready, status, restarts, age.

   

   The installation of the stream-processor-asi and the stream-processor-simulcrypt controls is optional. They should not be present on your system unless you have chosen to install them and executed the additional installation steps as described in the installation guides.

2. Verify that the status is “Running” for all the pods. If this is not the case, the system may not behave as expected.

3. Type kubectl delete pod <pod name\> -n mediakind where <pod_name> is the name of the pod associated to the microservice of interest as it appears in the output of the previous command.

   For example, to delete the mux pod in the previous deployment, you need to type kubectl delete pod stream-processor-config-8774bf6c-8gwkr -n mediakind.

   The string pod <pod name> deleted appears, which means that the pod has been successfully deleted.

4. Type kubectl get pods -n mediakind | grep stream-processor again to check that a new pod for the microservice is running.

The full name of the new pod is different than the previous one.

After the Mux pod has been deleted from the previous deployment, the new name can be “stream-processor-mux-c6f5f5579-f82mz”.

To view a specific microservice configuration:

1. Type kubectl get configmap -n mediakind | grep stream-processor. A list of configmaps appears with some information associated to each of them: name, ready, status, restarts, age.

   

   The installation of the stream-processor-asi and the stream-processor-simulcrypt controls is optional. They should not be present on your system unless you have chosen to install them and executed the additional installation steps as described in the installation guides.

2. Type kubectl get configmap -n mediakind <configmap> -o yaml where <configmap> is the name of the configmap associated to the microservice of interest as it appears in the output of the previous command.

The output contains all the configuration parameters for the specified microservice.

To check the announcer muticast information for the Mux microservice, type kubectl get configmap -n mediakind stream-processor-mux-config -o yaml and search for the announcer part of the sparkmuxIni.json: section. It should look like this, but with a different value for the multicastAddr field, depending on your deployment and installation options:

To edit a specific microservice configuration:

1. Type kubectl get configmap -n mediakind | grep stream-processor.

2. Type kubectl edit configmap -n mediakind <configmap> where <configmap> is the name of the configmap associated to the microservice of interest as it appears in the output of the previous command. The configmap is now open in vi editor and can be edited.

3. Apply your changes and save the configmap.

4. Restart the microservice.

   Although the changes have been saved in the configmap and can be viewed, they will not be applied by the microservice code until it is restarted.