Bump version

VERSION

@@ -1,2 +1,2 @@
-VERSION="v3.9.2_6.8.0"
+VERSION="v3.9.3_6.8.1"
 REVISION="3901"

elastic_stack/elasticsearch/cluster/elasticsearch-data-sts.yaml

@@ -52,7 +52,7 @@ spec:
             privileged: true
       containers:
         - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-elasticsearch:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

elastic_stack/elasticsearch/cluster/elasticsearch-master-sts.yaml

@@ -52,7 +52,7 @@ spec:
             privileged: true
       containers:
         - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-elasticsearch:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

elastic_stack/elasticsearch/single-node/elasticsearch-sts.yaml

@@ -52,7 +52,7 @@ spec:
             privileged: true    
       containers:
         - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-elasticsearch:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

elastic_stack/kibana/kibana-deploy.yaml

@@ -25,7 +25,7 @@ spec:
     spec:
       containers:
         - name: wazuh-kibana
-          image: 'wazuh/wazuh-kibana:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-kibana:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 200m

elastic_stack/kibana/nginx-deploy.yaml

@@ -25,7 +25,7 @@ spec:
     spec:
       containers:
         - name: wazuh-nginx
-          image: 'wazuh/wazuh-nginx:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-nginx:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 100m

elastic_stack/logstash/logstash-deploy.yaml

@@ -25,7 +25,7 @@ spec:
     spec:
       containers:
         - name: wazuh-logstash
-          image: 'wazuh/wazuh-logstash:3.9.2_6.8.0'
+          image: 'wazuh/wazuh-logstash:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

instructions.md

@@ -29,15 +29,15 @@ This pod contains the master node of the Wazuh cluster. The master node centrali
 The management is performed only in this node, so the agent registration service (authd) and the API are placed here.
 
 Details:
-- Image: Docker Hub 'wazuh/wazuh:3.9.2_6.8.0'
+- Image: Docker Hub 'wazuh/wazuh:3.9.3_6.8.1'
 - Controller: StatefulSet
 
 #### Wazuh worker 0 / 1
 
 These pods contain a worker node of the Wazuh cluster. They will receive the agent events.
 
 Details:
-- Image: Docker Hub 'wazuh/wazuh:3.9.2_6.8.0'
+- Image: Docker Hub 'wazuh/wazuh:3.9.3_6.8.1'
 - Controller: StatefulSet
 
 
@@ -46,7 +46,7 @@ Details:
 Elasticsearch pod. It receives and stores alerts received from Logstash. No Elasticsearch cluster is supported yet.
 
 Details:
-- Image: wazuh/wazuh-elasticsearch:3.9.2_6.8.0
+- Image: wazuh/wazuh-elasticsearch:3.9.3_6.8.1
 - Controller: StatefulSet
 
 
@@ -55,7 +55,7 @@ Details:
 Logstash pod. It receives the alerts from each Filebeat located in every Wazuh manager. Then, the alerts are sent to Elasticsearch.
 
 Details:
-- image: Docker Hub 'wazuh/logstash:3.9.2_6.8.0'
+- image: Docker Hub 'wazuh/logstash:3.9.3_6.8.1'
 - Controller: Deployment
 
 
@@ -64,15 +64,15 @@ Details:
 Kibana pod. It lets you visualize your Elasticsearch data, along with other features as the Wazuh app.
 
 Details:
-- image: Docker Hub 'wazuh/kibana:3.9.2_6.8.0'
+- image: Docker Hub 'wazuh/kibana:3.9.3_6.8.1'
 - Controller: Deployment
 
 #### Nginx
 
 The nginx pod acts as a reverse proxy for a safer access to Kibana.
 
 Details:
-- image: Docker Hub 'wazuh/nginx:3.9.2_6.8.0'
+- image: Docker Hub 'wazuh/nginx:3.9.3_6.8.1'
 - Controller: Deployment
 
 

upgrade.md

@@ -27,12 +27,12 @@ Any file that we modify referring to the files previously mentioned, will be cha
 
 To better understand it, we will give an example:
 
-We have our newly created Kubernetes environment following our instructions. In this example, the image of Wazuh used has been `wazuh/wazuh:3.9.2_6.8.0`.
+We have our newly created Kubernetes environment following our instructions. In this example, the image of Wazuh used has been `wazuh/wazuh:3.9.3_6.8.1`.
 
 ```
 containers:
 - name: wazuh-manager
-  image: 'wazuh/wazuh:3.9.2_6.8.0'
+  image: 'wazuh/wazuh:3.9.3_6.8.1'
 ```
 
 Let's proceed by creating a set of rules in our `local_rules.xml` file at location `/var/ossec/etc/rules` in our wazuh manager master pod. 
@@ -187,7 +187,7 @@ And now we're going to upgrade to the next version:
 ```
 containers:
 - name: wazuh-manager
-  image: 'wazuh/wazuh:3.9.2_6.8.0'
+  image: 'wazuh/wazuh:3.9.3_6.8.1'
 ```
 
 

wazuh_managers/wazuh-master-sts.yaml

@@ -33,7 +33,7 @@ spec:
             name: wazuh-manager-master-conf
       containers:
         - name: wazuh-manager
-          image: 'wazuh/wazuh:3.9.2_6.8.0'
+          image: 'wazuh/wazuh:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

wazuh_managers/wazuh-worker-0-sts.yaml

@@ -47,7 +47,7 @@ spec:
             name: wazuh-manager-worker-0-conf
       containers:
         - name: wazuh-manager
-          image: 'wazuh/wazuh:3.9.2_6.8.0'
+          image: 'wazuh/wazuh:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m

wazuh_managers/wazuh-worker-1-sts.yaml

@@ -47,7 +47,7 @@ spec:
             name: wazuh-manager-worker-1-conf
       containers:
         - name: wazuh-manager
-          image: 'wazuh/wazuh:3.9.2_6.8.0'
+          image: 'wazuh/wazuh:3.9.3_6.8.1'
           resources:
             requests:
               cpu: 500m