Notes for all versions

Updating CRDs

Some upgrades include changes to Custom Resource Definitions (CRDs).

If you are using the automated CRD updater tool bundled with the KNIME Business Hub application, CRDs are updated automatically during the upgrade.

If you have disabled the updater and installed CRDs manually, make sure to re-apply the latest CRDs from the public repository after each upgrade.

Outdated CRDs can cause issues such as executor errors or failed component deployments.

KNIME Business Hub version 1.16

Important notice for existing customers (32 GiB RAM instances)

Previously, a Hub instance with 32 GiB of RAM could host executors configured with up to 12 GiB of memory. After this update, the maximum executor size must be reduced to 8 GiB before starting the upgrade (Editing Executor Configuration). If executor memory is not adjusted, executors will fail to start until their configuration is lowered.

For customers on instances with more than 32 GiB RAM

In some cases, a large share of memory may already be reserved for execution. To ensure smooth operation, core services now require 24 GiB, leaving the remainder available for execution. Please adjust your executor memory accordingly before the update.

KURL-related infrastructure changes

Updated KURL installer (KURL Installer), bringing the following updates and more:

  • Kubernetes update to 1.33.4 (from 1.30.7 compared to last KURL update)

  • KOTS installer update to 1.125.2

  • Velero update to 1.16.2

Updated RoleBinding for license validation

With this release the RoleBinding used for license validation has been updated with additional ServiceAccount references. If you’ve installed KNIME Business Hub with Minimal RBAC you need to apply the updated Cluster Roles as described here before updating.

Upgrading Existing Argo CD Installations

For clusters where KNIME Business Hub was previously installed and managed via Argo CD, ensure the following configuration adjustments before upgrading to this release:

  1. Navigate to Settings → Projects → knime-business-hub.

  2. Under Namespaces, set this resource to Denied in the project configuration.

  3. In the Cluster Resource Allow List, allow all resources (*).

  4. In the Cluster Resource Deny List, deny at least the Namespaces resource.

  5. In the Namespace Resource Allow List, allow all resources (*).

These settings ensure a safe and consistent upgrade path for existing deployments managed by Argo CD.

KNIME Business Hub version 1.15

Istio upgrade

Istio has been upgraded to version 1.24.2.

  • For installations that have manually installed istio it is highly recommended to update istio to the same version. Instructions are available here.

  • For installations that install istio via KOTS, no other input is required. The upgrade will be automatic.

This upgrade will be mandatory in future releases when features only found in istio 1.24 are in use.