Victor Ereñú

The previous nomenclature separated two environments (4.2.x version): - production-cluster.yml which displayed a production environment with cluster included and persistence in all necessary directories. - docker-compose.yml which contains an example...

Hello @actionhenkt Can you tell me how you are activating Vulnerability Detector? Depending on what type of deployment you are doing, you will have to modify 1 or 2 files...

The Wazuh installation test was performed on a container, which managed to run without Filebeat, and it is also verifying which directories need to be exposed so that Filebeat feeds...

Two new Dockerfiles were created for the deployment of a container with Wazuh Manager alone and also an image with Filebeat, which will be fed from the volumes of the...

The Wazuh Manager and Filebeat images were generated, with them a deployment was tested, creating a new version of the production-cluster.yml file to display the entire application with these new...

Wazuh Manager was started inside a container alone with Ubuntu Focal, which weighs much less than Centos 7 and it was checked that it does not generate errors. Filebeat image...

Two new Dockerfiles were created, which generate the Wazuh Manager image alone and the Filebeat image. A new file called `production_cluster_mng_fb.yml` was created which generates the stack deployment with these...

We are awaiting confirmation to apply this development.

An investigation was carried out to implement a solution in Kubernetes to the problem generated by the separation of Wazuh Manager and Filebeat from the wazuh-odfe container. For the solution,...

Changes were applied to separate Wazuh Manager and Filebeat on the 4.2 branch, which contains the changes from release 4.2.4. The [506-deploy-with-manager-and-filebeat-sidecar](https://github.com/wazuh/wazuh-kubernetes/tree/506-deploy-with-manager-and-filebeat-sidecar) branch was created with the changes to test...