6.1. Overview#
This chapter collects various topics about the configuration of Nubus for Kubernetes.
6.1.1. Available configurations#
6.1.2. Apply configuration#
In many sections you come to the point where you need to apply the changes to Nubus for Kubernetes. This step is the same for most of them. To reduce duplicate content, you find the needed steps here. The affected sections refer back here.
To apply the updated configuration from the values file, use the following steps:
Set environment variables for the Helm command. Use the commands in Listing 3.3.
To upgrade your Nubus deployment, run the command in Listing 6.1.
$ helm upgrade "$RELEASE_NAME" \ --namespace "$NAMESPACE_FOR_NUBUS" \ --values custom_values.yaml \ --version "$VERSION" \ oci://artifacts.software-univention.de/nubus/charts/nubus
6.1.3. Restart UMC Server pod#
For some changes you need to restart the UMC Server pod. You usually come to this section, because the respective sections refer here to apply and complete the necessary steps.
Use the commands in Listing 6.2. They find out the name of the pod for the UMC Server and delete the pod. Kubernetes automatically recreates the pod with the updated configuration.
$ kubectl --namespace "$NAMESPACE_FOR_NUBUS" \
get pods \
| grep "umc-server-0"
nubus-umc-server-0 2/2 Running 0 4m33s
# Name of the pod is "nubus-umc-server-0"
$ kubectl --namespace "$NAMESPACE_FOR_NUBUS" \
delete pod "$NAME_OF_YOUR_POD"