Victor Ereñú

The Kubernetes manifest was modified to take the Wazuh Manager and Filebeat containers, the volumes to mount were modified but at the time of deployment, the Filebeat container does not...

The volume mount was configured as ReadWriteMany so that the volume can be mounted in the two containers within the Wazuh Manager prod but it did not start it, the...

We was investigated regarding the creation of PVs and PVCs from AWS EFS and I found a helm chart for their generation: ``` resource "helm_release" "efs-provisioner" { chart = "efs-provisioner"...

The creation of a new CSI driver for dynamic provisioning of EFS within the EKS cluster was verified. The following driver was deployed: https://github.com/kubernetes-sigs/aws-efs-csi-driver This driver has functionalities for manual...

EFS Tested Successfully. To mount these units, several steps were necessary: - Installation of the CSI driver for EFS - Creation of FS in EFS. - Creation of roles and...

The entire Wazuh stack could be started with the modifications so that Manager and Filebeat run in separate containers, being generated within the same Pod by the statefulset ``` $...

The replacement of the parameters used by filebeat was only done if there were lines marked with the "#" symbol, a step that was modified to eliminate these symbols if...

Hello @rpoulard Sorry for the delay in response. As of version 4.3, when starting the Wazuh manager container, a verification of the owner users of the application files is performed....

Hello @ryangniadek The configuration you are seeing was for **Opendistro**. Currently the stack deployed in version v4.3.6 contains **Wazuh Indexer**, which is based on **Opensearch**, so the directory you are...

I was reviewing the creation of the managed k8s cluster in Google Cloud and it exceeded the limit of CPU and IP addresses of quota, so I sent a request...