Changelog of the base of the orchestrator
5.32 (2026-10-06)
This version contains breaking changes. Actions to perform during the update are flagged with Migration.
- Renamed the
webservice toweb-application- Migration: in the custom configuration files of the
/etc/cyberwatch/configs-enableddirectory, rename thewebservice toweb-application, otherwise the Cyberwatch deployment fails
- Migration: in the custom configuration files of the
- Switched nginx to the unprivileged
nginx-rootlessimage- Migration: when containers are isolated by namespace, the
CBW_NGINX_UIDandCBW_NGINX_GIDvariables of theconfig.envfile must now match user 101 of the containers, and no longerroot(see nginx certificate folder)
- Migration: when containers are isolated by namespace, the
- Replaced Certbot with the nginx ACME module
- Deprecated: the
--certbotoption of thecyberwatch configurecommand is replaced by the--acmeoption - Removed the
certbotcontainer - Automatic migration of existing Certbot configurations, keeping the domain name
- Deprecated: the
- Switched to
cosign3 or later, provided with thecyberwatchpackage- Migration: in offline mode, update the
cosignpackage at the same time as thecyberwatchpackage
- Migration: in offline mode, update the
- Added the
cyberwatch renew-certificatescommand to renew the Cyberwatch internal TLS certificates - Added the
--force-pulloption to thecyberwatch startandcyberwatch restartcommands to download the images even if theCBW_NO_PULLvariable is enabled in theconfig.envfile cyberwatch restartnow continues the restart with the images already present on the node when it fails to download the new images- Display of
mysqldumpandmysqlerrors whencyberwatch backup saveorcyberwatch backup restorefails - Fixed the
--no-pulloption being ignored by thecyberwatch startcommand - Fixed the
CBW_DISABLE_ELKvariable not being taken into account when runningcyberwatch stopfollowed bycyberwatch start
5.31 (2026-07-09)
- Storage of nginx certificates in the
/etc/cyberwatch/ssldirectory instead of a Docker volume- Automatic migration of existing certificates during the update
- Ability to disable the deployment of Elasticsearch and Kibana via the
CBW_DISABLE_ELKvariable in theconfig.envfile - Web interface disabled by default on satellite nodes via the
ONLY_API_AND_THIRD_PARTIESvariable in thecontainers.envfile (during installation or after regenerating the configuration) - Support for a custom port for the backup and restore of an external database via the
MYSQL_PORTvariable in thecontainers.envfile - Added asynchronous cleanup of unused images
- If the timeout is exceeded at startup, the cleanup is postponed to a scheduled nightly task executed when the stack is stable
- The cleanup is skipped if the
CBW_DONT_PRUNE_UNUSED_IMAGESvariable is enabled in theconfig.envfile
5.30 (2026-04-10)
- Enabled user management in Kibana
- Fixed nginx certificate regeneration when using the
cyberwatch configurecommand - Fixed a warning during certificate generation on satellite nodes
5.29 (2026-03-18)
- Updated the validity period of certificates used by the application:
- 10 years for the root certificate
- 1 year for service certificates
- Automatic renewal of service certificates:
- 45 days before expiration by default
- The renewal period can be changed by setting the
CERT_RENEWAL_DAYSvariable in theconfig.envfile
- Use of the root certificate for database backup and restore:
- For instances using an external database, the certificate used is the one concatenated in the
cbw-root-ca-cert.pemfile
- For instances using an external database, the certificate used is the one concatenated in the
- Ability to configure the number of replicas for the following services via variables in the
config.envfile:- web with the
CBW_WEB_REPLICASvariable - sidekiq_node with the
CBW_SIDEKIQ_NODE_REPLICASvariable - container-scanner with the
CBW_CONTAINER_SCANNER_REPLICASvariable
- web with the
- Added a storage space check for containers (
/var/lib/containerd) via thecbw doctorcommand - Fixed an issue with adding
API_KEYSto the secret file - Fixed the minimum required Docker version for apt and rpm packages
5.28 (2025-11-28)
- Added timestamp to Cyberwatch update logs in
/var/log/cyberwatch.log - Fixed generation of empty backup file when a backup is interrupted
- Fixed warning message related to security options in the container-scanner container
5.27 (2025-04-09)
- Added a check during container startup to prevent the deletion of images for containers that have not yet been started
- Fixed the display of a warning related to the use of the
CBW_DONT_PRUNE_UNUSED_IMAGESoption - New images are now pulled before stopping the stack to minimize application downtime
5.26 (2025-03-18)
- Fixed a volume issue when configuring a node as an offline satellite
- Removed support for MicroK8s orchestrator
- The IP address of the Docker network used for container-scanner has been configured to be in a similar range to the default Docker network