Skip to main content Changelog of the base of the orchestrator
5.21 (2024-10-07)
- Remove the migration from cbw-on-premise v2.X to cbw-on-premise 5.X.
- The new procedure involves reinstalling Cyberwatch. Do not hesitate to contact support for more information.
- The web, sidekiq, sidekiq_master and sidekiq_node containers are now run with a non-privileged user.
- Remove the cron service.
- Added a sidekiq_master service available only on the master node.
5.20 (2024-08-22)
- Fixed a problem with the docker network for container scanning during restarts.
- Fixed
cyberwatch exec
command when used on a replicated service.
5.19 (2024-07-24)
- Fix a network error with network for container scanner that can occurs with power failure.
5.18 (2024-06-14)
- Added Buildah engine to scan docker container docker.
- Containers Redis and MariaDB are now run with non-privileged user.
- Correction of exit code returned on successful execution of orchestrator configuration command (
cyberwatch configure
)
5.17 (2024-05-16)
- Fixed compatibility problem with Bash versions < 4.4.
5.16 (2024-05-03)
- Fixed a problem related to the generation of the root certificate introduced in 5.14.
5.15 (2024-04-30)
- Remove CPU resource limitation for Docker containers with Swarm, introduced in version 5.14.
5.14 (2024-04-25)
- Added memory and processor resource limitation for Docker containers with Swarm.
- Automatic removal of the
version
field in Docker Compose files. - Automatic scaling to two Sidekiq replicas when the machine hosting Cyberwatch has more than four processors.
- Improved the TLS certificate generation steps, when configuring the orchestrator base with Swarm.
- Multiple fixes to ensure compatibility with Docker Engine versions higher than 25.2.
- Minimal version supported of the Docker Engine is now 23.0.6.
5.13 (2024-01-05)
- Added a
--no-pull
option to the command to start Cyberwatch without pulling new Docker images (cyberwatch start
command). - Added a
--no-redis
option to the command to configure an external Redis server (cyberwatch configure
command). - Added a
CBW_NO_PULL
variable in the orchestrator base configuration file to disable the pull of new Docker images. - Added missing options in the Bash completion of Cyberwatch commands.
- Helm versions lower than 3.7.0 are no longer supported.
5.12 (2023-12-11)
- Added a
--no-pull
option to the command to restart Cyberwatch without pulling new Docker images (cyberwatch restart
command). - Added a
CBW_SIDEKIQ_REPLICAS
variable in the orchestrator base configuration file to increase the number of Sidekiq replicas. - Fixed a problem related to the use of an external Redis.
- Fixed an infinite loop problem that could occur when stopping the application when the orchestrator is Swarm (
cyberwatch stop
command). - Fixed an issue with the command checking the orchestrator base status, when checking for database backups (
cyberwatch doctor
command). - Fixed error code returned when executing a command on a running container (
cyberwatch exec
command). - TLS certificates for master and satellite nodes are now valid for five years.
5.11 (2023-07-24)
- Revert the fix for external Redis.
5.10 (2023-07-21)
- Images signatures are now verified with Cosign.
- Limit Elasticsearch memory usage to 1.5 GB.
- Fixed a problem related to the use of an external Redis.
- Application update/restart from GUI: database backup problem fixed.
5.9 (2022-11-17)
- Added a new container called “web-scanner” dedicated to scanning network targets and websites.
- Ease the configuration of environment variables with Swarm.
- Manage TLS for MariaDB for Swarm