wazuh/wazuh-kubernetes
1
0
Fork 0
mirror of https://github.com/wazuh/wazuh-kubernetes.git synced 2025-12-10 00:38:21 -06:00
Code Issues Packages Projects Releases 100 Wiki Activity

Bump version to 3.13.0_7.7.1

Browse Source
This commit is contained in:
Manuel Gutierrez 2020-06-23 18:44:56 +02:00
parent af2bfbea4d
commit 7c0c62765f
No known key found for this signature in database
GPG Key ID: CEB8789DAED15AAD
12 changed files with 26 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CHANGELOG.md
View File

@ -2,6 +2,12 @@
All notable changes to this project will be documented in this file.
## [v3.13.0]
### Added
- Update to Wazuh version 3.13.0_7.7.1
## [v3.12.3]
### Added

4
VERSION
View File

@ -1,2 +1,2 @@
VERSION="v3.12.3_7.6.2"
REVISION="31230"
VERSION="v3.13.0_7.7.1"
REVISION="31300"

2
elastic_stack/elasticsearch/cluster/elasticsearch-data-sts.yaml
View File

@ -52,7 +52,7 @@ spec:
privileged: true
containers:
- name: wazuh-elasticsearch
image: 'wazuh/wazuh-elasticsearch:3.12.3_7.6.2'
image: 'wazuh/wazuh-elasticsearch:3.13.0_7.7.1'
resources:
requests:
cpu: 500m

2
elastic_stack/elasticsearch/cluster/elasticsearch-master-sts.yaml
View File

@ -52,7 +52,7 @@ spec:
privileged: true
containers:
- name: wazuh-elasticsearch
image: 'wazuh/wazuh-elasticsearch:3.12.3_7.6.2'
image: 'wazuh/wazuh-elasticsearch:3.13.0_7.7.1'
resources:
requests:
cpu: 500m

4
elastic_stack/elasticsearch/single-node/elasticsearch-sts.yaml
View File

@ -52,7 +52,7 @@ spec:
privileged: true
containers:
- name: wazuh-elasticsearch
image: 'wazuh/wazuh-elasticsearch:3.12.3_7.6.2'
image: 'wazuh/wazuh-elasticsearch:3.13.0_7.7.1'
resources:
requests:
cpu: 500m
@ -89,4 +89,4 @@ spec:
storageClassName: gp2-encrypted-retained
resources:
requests:
storage: 30Gi
storage: 30Gi

2
elastic_stack/kibana/kibana-deploy.yaml
View File

@ -25,7 +25,7 @@ spec:
spec:
containers:
- name: wazuh-kibana
image: 'wazuh/wazuh-kibana:3.12.3_7.6.2'
image: 'wazuh/wazuh-kibana:3.13.0_7.7.1'
resources:
requests:
cpu: 200m

2
elastic_stack/kibana/nginx-deploy.yaml
View File

@ -25,7 +25,7 @@ spec:
spec:
containers:
- name: wazuh-nginx
image: 'wazuh/wazuh-nginx:3.12.3_7.6.2'
image: 'wazuh/wazuh-nginx:3.13.0_7.7.1'
resources:
requests:
cpu: 100m

10
instructions.md
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.12.3_7.6.2'
- Image: Docker Hub 'wazuh/wazuh:3.13.0_7.7.1'
- 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.12.3_7.6.2'
- Image: Docker Hub 'wazuh/wazuh:3.13.0_7.7.1'
- Controller: StatefulSet
@ -46,7 +46,7 @@ Details:
Elasticsearch pod. No Elasticsearch cluster is supported yet.
Details:
- Image: wazuh/wazuh-elasticsearch:3.12.3_7.6.2
- Image: wazuh/wazuh-elasticsearch:3.13.0_7.7.1
- 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.12.3_7.6.2'
- image: Docker Hub 'wazuh/kibana:3.13.0_7.7.1'
- 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.12.3_7.6.2'
- image: Docker Hub 'wazuh/nginx:3.13.0_7.7.1'
- Controller: Deployment

8
upgrade.md
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.12.3_7.6.2`.
We have our newly created Kubernetes environment following our instructions. In this example, the image of Wazuh used has been `wazuh/wazuh:3.13.0_7.7.1`.
```
containers:
- name: wazuh-manager
image: 'wazuh/wazuh:3.12.3_7.6.2'
image: 'wazuh/wazuh:3.13.0_7.7.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.12.3_7.6.2'
image: 'wazuh/wazuh:3.13.0_7.7.1'
```
@ -202,4 +202,4 @@ statefulset.apps "wazuh-manager-master" configured
This process will end the old pod while creating a new one with the new version, linked to the same volume. Once the Pods are booted, we will have our update ready and we can check the new version of Wazuh installed, the cluster and the changes that have been maintained through the use of the volumes.
### Note: It is important to update all Wazuh node pods, because the cluster only works when all nodes have the same version.
### Note: It is important to update all Wazuh node pods, because the cluster only works when all nodes have the same version.

2
wazuh_managers/wazuh-master-sts.yaml
View File

@ -33,7 +33,7 @@ spec:
name: wazuh-manager-master-conf
containers:
- name: wazuh-manager
image: 'wazuh/wazuh:3.12.3_7.6.2'
image: 'wazuh/wazuh:3.13.0_7.7.1'
resources:
requests:
cpu: 2

2
wazuh_managers/wazuh-worker-0-sts.yaml
View File

@ -47,7 +47,7 @@ spec:
name: wazuh-manager-worker-0-conf
containers:
- name: wazuh-manager
image: 'wazuh/wazuh:3.12.3_7.6.2'
image: 'wazuh/wazuh:3.13.0_7.7.1'
resources:
requests:
cpu: 2

2
wazuh_managers/wazuh-worker-1-sts.yaml
View File

@ -47,7 +47,7 @@ spec:
name: wazuh-manager-worker-1-conf
containers:
- name: wazuh-manager
image: 'wazuh/wazuh:3.12.3_7.6.2'
image: 'wazuh/wazuh:3.13.0_7.7.1'
resources:
requests:
cpu: 2