Migration of KNIME Business Hub from v4.7 to v5

Hi, my name’s Matt, working on a project which will make use of KNIME business hub to run workflows that we generate with the analytics platform.

However, when I try to deploy KNIME hub to the latest resource available (needed because some of the workflows generated use KNIME analytics platform version 5, while the hub was on version 4.7), I observe an error initially due to Kubernetes version (originally started at 1.23.4, migrated up to 1.27.2 mostly to ensure longevity of the system), and relating to the KOTS version, which is blocking the associated deployment.

This is a single VM system deployment on a single Azure VM with sufficient capability to run the Hub (community edition).

I’ve followed the instructions for upgrading Kubernetes (which is now at version 1.27.8 on the server/cluster), but the KOTS version cannot be updated.

I’ve updated the kots version on the CLI, but a warning still flags regarding the API version (it is not super clear from the KOTS documentation how to resolve this).


$ kubectl kots version
Replicated KOTS 1.102.2 # This version number is greater than the minimum

Version v1.104.7 is available for kots. To install updates, run
  $ curl https://kots.io/install | bash
  • KOTS CLI version 1.102.2 does not match API version 1.96.3. To update, run:
  $ curl https://kots.io/install/1.96.3 | bash

Previous version of KOTS was 1.96.3 (prior to migration), with the new version being 1.102.2 (which is greater than the minimum for the deployment).

Since I’m not super familiar with the kubernetes administration regarding the migration, does anyone have a good cheat sheet of actions needed to migrate for each step?

I think I’ve got most of them, but a few are hard to catch (I think the KOTS API error relates to the fact that a cluster version of kots was not updated, but its not clear how to update this version).

I have full sudo privileges available, and the edition is “Community Edition” if relevant.

Are there any specific pieces I might be missing when undertaking the migration? Kubernetes administration is somewhat tricky to track through if you’re not careful.


Matt A

Other diagnostic info:

$ kubectl version

WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.8", GitCommit:"66fee42707cd7f5a89f1987f7cb81b02dd19161c", GitTreeState:"clean", BuildDate:"2023-11-15T16:59:43Z", GoVersion:"go1.20.11", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.8", GitCommit:"66fee42707cd7f5a89f1987f7cb81b02dd19161c", GitTreeState:"clean", BuildDate:"2023-11-15T16:50:09Z", GoVersion:"go1.20.11", Compiler:"gc", Platform:"linux/amd64"}

Hi Matt,
How did you update the Kubernetes version? Did you do it by running the Kurl installer from command line?

Just a side note: to use a newer executor version (e.g. 5.2 instead of 4.7), you can just edit your execution context and set a new executor image. For 5.2 that would be registry.hub.knime.com/knime/knime-full:r-5.2.0-271. There’s no need to update Business Hub for that. A list of all public executor images is available here.
Kind regards,

1 Like