6.1.5. Scalability#
Nubus for Kubernetes consists of several components. Some of the components allow you to scale them to your needs. This section describes which components you can scale up in Nubus and how you configure it.
Usually, the default replica count for each component is 1
.
To change the scalability of the mentioned components, you need to apply the following principle:
Update your
custom_values.yaml
deployment file with the appropriate setting as described for each component later in this section.Update your Nubus deployment through helm by following the steps in Apply configuration.
See also
- Scalability architecture in Nubus for Kubernetes
in Univention Nubus for Kubernetes - Architecture Manual [2] for the architectural description of the scalability of the functional components in Nubus for Kubernetes.
6.1.5.1. Directory Manager#
The Directory Manager has the UDM HTTP REST API as scalable component.
To configure the scalability of the UDM HTTP REST API,
set nubusUdmRestApi.replicaCount
to an integer value greater than the default value.
To apply configuration changes, see instructions at Scalability.
Important
Take the scalability considerations from Directory Manager in Univention Nubus for Kubernetes - Architecture Manual [2] into account.
6.1.5.2. Management UI#
The Management UI has the following scalable components.
- UMC-Server
To configure the scalability of the UMC Server, set
nubusUmcServer.replicaCount
to an integer value greater than the default value.The UMC Server also has the setting
nubusUmcServer.proxy.replicaCount
for the load balancer with session stickiness. Change the value to an integer value greater than the default value.- UMC-Gateway
To configure the scalability of the UMC Gateway, set
nubusUmcGateway.replicaCount
to an integer value greater than the default value.
In a high-traffic environment, it’s more important to scale up the UMC Server than the UMC Gateway.
To apply configuration changes, see instructions at Scalability.
See also
- Management UI
in Univention Nubus for Kubernetes - Architecture Manual [2] for architectural information about the scalability of the Management UI.
6.1.5.3. Identity Provider#
The Identity Provider has the following scalable components.
- Keycloak
To configure the scalability of Keycloak set
keycloak.replicaCount
to an integer value greater than the default value.- Keycloak Proxy
If your Nubus for Kubernetes deployment has the Keycloak Extensions enabled, you can scale up the Keycloak Proxy in the Keycloak Extensions. Scale it up along with the scaling of the Keycloak Kubernetes pod.
To configure the scalability of the Keycloak Proxy set
nubusKeycloakExtensions.proxy.replicaCount
to an integer value greater than the default value.
To apply configuration changes, see instructions at Scalability.
See also
- Enable Keycloak Extensions
for information about how to enable Keycloak Extensions.
- Identity Provider
in Univention Nubus for Kubernetes - Architecture Manual [2] for architectural information about the scalability of the Identity Provider.
6.1.5.4. Portal Service#
The Portal Service has the following scalable components:
- Portal Server
To configure the scalability of the Portal Server set
nubusPortalServer.replicaCount
to an integer value greater than the default value.- Portal Frontend
To configure the scalability of the Portal Frontend set
nubusPortalFrontend.replicaCount
to an integer value greater than the default value.
In a high-traffic environment, it’s more important to scale up the Portal Server Kubernetes pod than the Portal Frontend pod, because the Portal Server actively handles requests from the Portal Frontend and determines the portal content for each user.
To apply configuration changes, see instructions at Scalability.
See also
- Portal Service
in Univention Nubus for Kubernetes - Architecture Manual [2] for architectural information about the scalability of the Portal Service.
6.1.5.5. Identity Store and Directory Service#
For the scalability of the Identity Store and Directory Service, see Directory service high availability and scalability.