Bump version

This commit is contained in:
Manuel J. Bernal 2019-05-21 21:39:30 +02:00
parent f1f3ad1747
commit a74ff79d40
15 changed files with 47 additions and 19 deletions

View File

@ -2,6 +2,9 @@
All notable changes to this project will be documented in this file.
## [v3.9.1]
- Update to Wazuh version 3.9.1_6.8.0
## [v3.9.0]

View File

@ -1,2 +1,2 @@
VERSION="v3.9.0_6.7.2"
VERSION="v3.9.1_6.8.0"
REVISION="3901"

View File

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

View File

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

View File

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

View File

@ -25,7 +25,7 @@ spec:
spec:
containers:
- name: wazuh-kibana
image: 'wazuh/wazuh-kibana:3.9.0_6.7.2'
image: 'wazuh/wazuh-kibana:3.9.1_6.8.0'
resources:
requests:
cpu: 200m

View File

@ -25,7 +25,7 @@ spec:
spec:
containers:
- name: wazuh-nginx
image: 'wazuh/wazuh-nginx:3.9.0_6.7.2'
image: 'wazuh/wazuh-nginx:3.9.1_6.8.0'
resources:
requests:
cpu: 100m

View File

@ -25,7 +25,7 @@ spec:
spec:
containers:
- name: wazuh-logstash
image: 'wazuh/wazuh-logstash:3.9.0_6.7.2'
image: 'wazuh/wazuh-logstash:3.9.1_6.8.0'
resources:
requests:
cpu: 500m

View File

@ -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.9.0_6.7.2'
- Image: Docker Hub 'wazuh/wazuh:3.9.1_6.8.0'
- 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.9.0_6.7.2'
- Image: Docker Hub 'wazuh/wazuh:3.9.1_6.8.0'
- 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.0_6.7.2
- Image: wazuh/wazuh-elasticsearch:3.9.1_6.8.0
- 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.0_6.7.2'
- image: Docker Hub 'wazuh/logstash:3.9.1_6.8.0'
- Controller: Deployment
@ -64,7 +64,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.9.0_6.7.2'
- image: Docker Hub 'wazuh/kibana:3.9.1_6.8.0'
- Controller: Deployment
#### Nginx
@ -72,7 +72,7 @@ Details:
The nginx pod acts as a reverse proxy for a safer access to Kibana.
Details:
- image: Docker Hub 'wazuh/nginx:3.9.0_6.7.2'
- image: Docker Hub 'wazuh/nginx:3.9.1_6.8.0'
- Controller: Deployment

View File

@ -0,0 +1,11 @@
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: task-pv-claim
spec:
storageClassName: manual
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 3Gi

View File

@ -0,0 +1,14 @@
kind: PersistentVolume
apiVersion: v1
metadata:
name: task-pv-volume
labels:
type: local
spec:
storageClassName: manual
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/data"

View File

@ -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.0_6.7.2`.
We have our newly created Kubernetes environment following our instructions. In this example, the image of Wazuh used has been `wazuh/wazuh:3.9.1_6.8.0`.
```
containers:
- name: wazuh-manager
image: 'wazuh/wazuh:3.9.0_6.7.2'
image: 'wazuh/wazuh:3.9.1_6.8.0'
```
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.0_6.7.2'
image: 'wazuh/wazuh:3.9.1_6.8.0'
```

View File

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

View File

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

View File

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