Bump version to 3.10.2_7.3.2

2025-12-10 00:38:21 -06:00 · 2019-09-25 09:56:32 +02:00 · 2019-09-25 09:56:32 +02:00 · 688d43de7a
commit 688d43de7a
parent fedf767e0c
11 changed files with 18 additions and 18 deletions
--- a/4
+++ b/4
@ -1,2 +1,2 @@
-VERSION="v3.10.0_7.3.2"
-REVISION="31000"
+VERSION="v3.10.2_7.3.2"
+REVISION="31020"
--- a/elastic_stack/elasticsearch/cluster/elasticsearch-data-sts.yaml
+++ b/elastic_stack/elasticsearch/cluster/elasticsearch-data-sts.yaml
@ -52,7 +52,7 @@ spec:
            privileged: true
      containers:
        - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.10.0_7.3.2'
+          image: 'wazuh/wazuh-elasticsearch:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 500m
--- a/elastic_stack/elasticsearch/cluster/elasticsearch-master-sts.yaml
+++ b/elastic_stack/elasticsearch/cluster/elasticsearch-master-sts.yaml
@ -52,7 +52,7 @@ spec:
            privileged: true
      containers:
        - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.10.0_7.3.2'
+          image: 'wazuh/wazuh-elasticsearch:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 500m
--- a/elastic_stack/elasticsearch/single-node/elasticsearch-sts.yaml
+++ b/elastic_stack/elasticsearch/single-node/elasticsearch-sts.yaml
@ -52,7 +52,7 @@ spec:
            privileged: true    
      containers:
        - name: wazuh-elasticsearch
-          image: 'wazuh/wazuh-elasticsearch:3.10.0_7.3.2'
+          image: 'wazuh/wazuh-elasticsearch:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 500m
--- a/elastic_stack/kibana/kibana-deploy.yaml
+++ b/elastic_stack/kibana/kibana-deploy.yaml
@ -25,7 +25,7 @@ spec:
    spec:
      containers:
        - name: wazuh-kibana
-          image: 'wazuh/wazuh-kibana:3.10.0_7.3.2'
+          image: 'wazuh/wazuh-kibana:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 200m
--- a/elastic_stack/kibana/nginx-deploy.yaml
+++ b/elastic_stack/kibana/nginx-deploy.yaml
@ -25,7 +25,7 @@ spec:
    spec:
      containers:
        - name: wazuh-nginx
-          image: 'wazuh/wazuh-nginx:3.10.0_7.3.2'
+          image: 'wazuh/wazuh-nginx:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 100m
--- a/instructions.md
+++ b/instructions.md
@ -29,7 +29,7 @@ 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.10.0_7.3.2'
+- Image: Docker Hub 'wazuh/wazuh:3.10.2_7.3.2'
 - Controller: StatefulSet

 #### Wazuh worker 0 / 1
@ -37,7 +37,7 @@ Details:
 These pods contain a worker node of the Wazuh cluster. They will receive the agent events.

 Details:
- Image: Docker Hub 'wazuh/wazuh:3.10.0_7.3.2'
+- Image: Docker Hub 'wazuh/wazuh:3.10.2_7.3.2'
 - Controller: StatefulSet


@ -46,7 +46,7 @@ Details:
 Elasticsearch pod. No Elasticsearch cluster is supported yet.

 Details:
- Image: wazuh/wazuh-elasticsearch:3.10.0_7.3.2
+- Image: wazuh/wazuh-elasticsearch:3.10.2_7.3.2
 - Controller: StatefulSet

 #### Kibana
@ -54,7 +54,7 @@ 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.10.0_7.3.2'
+- image: Docker Hub 'wazuh/kibana:3.10.2_7.3.2'
 - Controller: Deployment

 #### Nginx
@ -62,7 +62,7 @@ Details:
 The nginx pod acts as a reverse proxy for a safer access to Kibana.

 Details:
- image: Docker Hub 'wazuh/nginx:3.10.0_7.3.2'
+- image: Docker Hub 'wazuh/nginx:3.10.2_7.3.2'
 - Controller: Deployment


--- a/upgrade.md
+++ b/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.10.0_7.3.2`.
+We have our newly created Kubernetes environment following our instructions. In this example, the image of Wazuh used has been `wazuh/wazuh:3.10.2_7.3.2`.

 ```
 containers:
 - name: wazuh-manager
-  image: 'wazuh/wazuh:3.10.0_7.3.2'
+  image: 'wazuh/wazuh:3.10.2_7.3.2'
 ```

 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.10.0_7.3.2'
+  image: 'wazuh/wazuh:3.10.2_7.3.2'
 ```


--- a/wazuh_managers/wazuh-master-sts.yaml
+++ b/wazuh_managers/wazuh-master-sts.yaml
@ -33,7 +33,7 @@ spec:
            name: wazuh-manager-master-conf
      containers:
        - name: wazuh-manager
-          image: 'wazuh/wazuh:3.10.0_7.3.2'
+          image: 'wazuh/wazuh:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 2
--- a/wazuh_managers/wazuh-worker-0-sts.yaml
+++ b/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.10.0_7.3.2'
+          image: 'wazuh/wazuh:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 2
--- a/wazuh_managers/wazuh-worker-1-sts.yaml
+++ b/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.10.0_7.3.2'
+          image: 'wazuh/wazuh:3.10.2_7.3.2'
          resources:
            requests:
              cpu: 2