General upgrade information

The process of upgrading a single, distributed, or clustered Kadeck Teams instance is straightforward. In many cases, you upgrade the software by installing the latest distribution over your existing installation.

The following requirements must be met for the upgrade, regardless of the type of deployment:

1. You need an active Kadeck Teams Administrator account.
   
2. You may need access to the Kadeck Teams database (see Upgrade Information of your version).
   
3. You need access to the infrastructure environment in which Kadeck Teams is running:
   
1. If Kadeck Teams is operated as a container, you need access to change environment variables and the container image.
   
2. If Kadeck Teams is run directly as an installation on a VM (e.g. also EC2) or server instance, you need operating system rights for the respective server/VM instances.

Please backup your database!

In most cases an upgrade from Kadeck Teams is irreversible. The database should always be backed up before an upgrade so that the changes can be rolled back if an error occurs during the upgrade.

 

Images and version numbers

See our Docker Hub for Docker container images.

Version 4.2.9 - Mar 2023 - Hotfix (Performance Issue with Schema Registry)

Version 4.2.7 - Mar 2023 - Kadeck Teams release (Update to new docker image xeotek/kadeck !)

Version 4.2.6 - Mar 2023

Version 4.2.5 - Mar 2023

Version 4.2.4 - Feb 2023

Version 4.2.3 - Feb 2023

Version 4.2.2 - Feb 2023

Version 4.2.1 - Feb 2023

Version 4.2.0 - Feb 2023

Version 4.1.5 - Dec 2022

Version 4.1.4 - Dec 2022

Version 4.1.3 - Nov 2022

Version 4.1.2 - Nov 2022

Version 4.1.1 - Nov 2022

Version 4.1.0 - Nov 2022

Version 4.0.0 - Sept 2022

Version 3.2.3 - May 2022

Version 3.2.2 - Apr. 2022

Version 3.2.1 - Mar. 2022

Version 3.2.0.1 - Feb. 2022 (security patch)

Version 3.2.0 - Feb. 2022

Version 3.1.9.4 - Jan. 2022 (security patch)

Version 3.1.9.3 - Dec. 2021 (security patch)

Version 3.1.9.2 - Dec. 2021 (security patch)

Version 3.1.9 - Okt. 2021 (updated on Dec. 2021 with security patch)

Version 3.1.8 - Jul. 2021 

Version 3.1.7 - Jul. 2021 

Version 3.1.6 - Jun. 2021 

Version 3.1.5 - Apr. 2021 

Version 3.0.1 - Dec. 2020

Version 3.0.0 - Nov. 2020 

Version 2.2.1 - Aug. 2020

Version 2.2.0 - Aug. 2020

Version 2.1.0 - Jul. 2020

 

Standard update/upgrade procedure

Update the deployed images of your Kadeck Teams installation to the respective version number.

Please create an update of the database before.

Kadeck will detect the previous version of the database and automatically perform an update procedure.

• Related Articles

• General SASL/Keberos configuration

  This article describes how to configure a server connection with SASL and Kerberos correctly. Introduction Kadeck supports a variety of configurations when connecting to a server using SASL. Supported security protocols SASL_PLAINTEXT SASL_SSL ...

• Release 4.2.9

  This article describes the changes of the version 4.2.x update. Note: We have released a 4.2.9 hotfix that solves a performance problem in connection with the schema registry, which led to an extremely long connection process or missing schemas for ...

• Release 4.3.0

  This article describes the changes of the version 4.3.x update. New image tag: xeotek/kadeck:4.3.0 Release 4.3.0 Many new views UX improvements for easier, better insights into your Apache Kafka data and performance. The consumer rights are now more ...

• Log File (Troubleshooting)

  Logs In general, the log file can be found in the current user's home directory. Before sending or looking at the file, it might be useful to change the log level to DEBUG (default is WARN) to capture the maximum amount of information possible to ...

• Troubleshooting

  If you have problems running Kadeck Teams, log output is very important for quick support. If possible, the problem should be recreated with the log level "DEBUG" and then the log output should be sent to Kadeck Support. Most of our customers use a ...