Version 1.10.x

Version 1.10.x#

This page shows the changelog for Nubus for Kubernetes 1.10.x:

Important

Bundled dependencies using Bitnami images (PostgreSQL, MinIO, Memcached) require configuration changes, because Bitnami migrated their repositories from docker.io/bitnami to docker.io/bitnamilegacy. Deployments that use external dependencies aren’t affected. For more information, see Bitnami GitHub issue #35164.

If you deploy these dependencies with Nubus, override the image repositories in your custom_values.yaml as shown in the following listing.

Listing 4 Adjust image repositories for bundled dependencies#
postgresql:
  image:
    repository: bitnamilegacy/postgresql
  provisioning:
    image:
      repository: bitnamilegacy/postgresql
minio:
  image:
    repository: bitnamilegacy/minio
nubusUmcServer:
  memcached:
    image:
      repository: bitnamilegacy/memcached

Version 1.10.2 - 2025-06-06#

This is the thirteenth production release of Nubus for Kubernetes.

Upgrade path

For the upgrade to version 1.10.2, your deployment must run on version 1.9.0 to 1.9.2. For the general steps to upgrade an existing Nubus for Kubernetes deployment, see Upgrade in Univention Nubus for Kubernetes - Operation Manual [1].

Migration steps#

This section lists necessary migration steps that may apply to you. You need to run them before the upgrade.

  1. Follow and apply the migration steps outlined in v1.10.0 - Migration steps.

Changes#

  • Correct the behavior of two Helm variables in the UDM REST API univentionObjectIdentifier migration job: The variables nubusUdmRestApi.ldapUpdateUniventionObjectIdentifier.image.imagePullPolicy and nubusUdmRestApi.ldapUpdateUniventionObjectIdentifier.image.registry are now effective at controlling the image registry and pull policy for the container image used in the job.

Version 1.10.1 - 2025-06-02#

This is the twelfth production release of Nubus for Kubernetes.

Upgrade path

For the upgrade to version 1.10.1, your deployment must run on version 1.9.0 to 1.9.2. For the general steps to upgrade an existing Nubus for Kubernetes deployment, see Upgrade in Univention Nubus for Kubernetes - Operation Manual [1].

Migration steps#

This section lists necessary migration steps that may apply to you. You need to run them before the upgrade.

  1. Follow and apply the migration steps outlined in v1.10.0 - Migration steps.

Changes#

  • Remove quotes from additional annotations in UDM REST API Blocklists cleanup job.

Version 1.10.0 - 2025-05-27#

This is the eleventh production release of Nubus for Kubernetes.

Upgrade path

For the upgrade to version 1.10.0, your deployment must run on version 1.9.0 to 1.9.2. For the general steps to upgrade an existing Nubus for Kubernetes deployment, see Upgrade in Univention Nubus for Kubernetes - Operation Manual [1].

Migration-steps#

This section lists necessary migration steps that may apply to you. You need to run them before the upgrade.

  1. Operators have to delete the following Keycloak clients from the Keycloak Admin Console before upgrading due to a wrong configuration that prohibited access to the Guardian:

    • guardian-scripts

    • guardian-management-api

    • guardian-ui

    The upgrade process recreates the proper client configuration in Keycloak.

  2. It’s necessary for operators to trigger the generation of the univentionObjectIdentifier for existing UDM objects and directory objects, because future releases of Nubus for Kubernetes rely on it.

    Recommendation:

    The Helm chart already creates a migration job in a suspended state. Run the migration job as shown in listing Listing 5 at a time with low system load on the cluster. It takes around 6 minutes per 100.000 LDAP objects.

    After a successful run, you can optionally deactivate the job by setting nubusUdmRestApi.ldapUpdateUniventionObjectIdentifier.enabled to false so that Kubernetes doesn’t create the job again. If you keep the job activated, it doesn’t have a negative impact.

    Listing 5 Run the migration job for univentionObjectIdentifier#
    $ kubectl patch job/<JOB_NAME> \
    --type=strategic \
    --patch '{"spec":{"suspend":false}}'

  3. Operators that make use of the following UDM Listener secrets variables, need to adjust these accordingly:

    • Rename nubusUdmListener.ldap.credentialSecret.* to nubusUdmListener.ldap.auth.existingSecret.*.

    • Rename nubusUdmListener.nats.auth.credentialSecret.* to nubusUdmListener.nats.auth.existingSecret.*

    • Rename nubusUdmListener.provisioningApi.auth.credentialSecret.* to nubusUdmListener.provisioningApi.auth.existingSecret.*

    • Move Provisioning username sourced from secret key in nubusUdmListener.provisioningApi.auth.credentialSecret.userNameKey to a non-secret value nubusUdmListener.provisioningApi.auth.username.

    For the structure of existingSecret, see Listing 6.

Changes#

On this page