You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Helm chart for Wazuh the open source security platform that unifies XDR and SIEM protection for endpoints and cloud workloads.
6
6
7
+
## Getting started
8
+
9
+
To get started, first install our helm repo
10
+
11
+
```bash
12
+
helm repo add josa https://charts.josa.ngo
13
+
helm repo update
14
+
```
15
+
16
+
Once your values.yaml configuration is ready use
17
+
18
+
**Read the [Configurations notes](#configurations-notes) before installing the chart**
19
+
20
+
```bash
21
+
helm install wazuh josa/wazuh
22
+
```
23
+
24
+
### Configurations notes
25
+
26
+
#### Release Name
27
+
28
+
We strongly recommend setting the release name to "wazuh" in order to avoid issues with the manager configuration. The reason for this is that the wazuh manager nodes uses the name "wazuh" by default.
29
+
30
+
If you want to change the name you will need to provide your own wazuh-manager configuration under `manager.config.customManagerConfig`.
31
+
32
+
You will need to provide your own `master.conf` and `worker.conf` in your config maps, containing the your release name.
33
+
34
+
**Example on the release name:**
35
+
36
+
If your release name is `my-release`, the manager node references in the configuration files should look like:
37
+
38
+
```yaml
39
+
my-release-manager-master-0.my-release-cluster
40
+
```
41
+
42
+
> Make sure that the cluster name matches the release name (my-release in this example)
43
+
44
+
**Example of the node name under `master.conf` and `worker.conf`:**
You can take a look at our configuration in our templates [here](./configs/wazuh_conf/).
63
+
64
+
#### TLS
65
+
66
+
We need to note that TLS is enabled and required at all times in our chart. In order to get this chart working you will need to provide the following tls configuration.
67
+
68
+
The easiest way, and the one we recommend is that you enable the certification creation in our chart if your cluster has [cert-manager](https://cert-manager.io/docs/installation/helm/) installed.
69
+
70
+
If you don't have a cert-manager. You can generate the required certificates and provide them as secrets under `tls.secretName`
71
+
72
+
The required certificates you will need in your secrets are the following:
73
+
74
+
- admin-key.pem
75
+
- admin.pem
76
+
- node-key.pem (referenced in the docs as index-key.pem and indexer.pem)
77
+
- node.pem
78
+
- root-ca.pem
79
+
- server.key
80
+
- server.cert
81
+
- key.pem
82
+
- cert.pem
83
+
- filebeat-key.pem
84
+
- filebeat.pem
85
+
86
+
For more information on how to generate these .pem files refer to the [wazuh Deployment kubernets](https://documentation.wazuh.com/current/deployment-options/deploying-with-kubernetes/kubernetes-deployment.html#setup-ssl-certificates)
87
+
> You may notice that we did not provide the files dashboard-key.pem and dashboard.pem.
88
+
>
89
+
>This is because the Wazuh Kubernetes setup uses multiple names for the same certificate. Specifically, it utilizes key.pem and cert.pem alongside dashboard.pem and dashboard-key.pem, even though they refer to the same underlying certificates.
90
+
>
91
+
>In other words, different names are used interchangeably for the same certificate files across the setup.
@@ -16,7 +106,7 @@ A Helm chart for Wazuh the open source security platform that unifies XDR and SI
16
106
| dashboard.config.secrets.existingSecretName | string |`""`| ----------------- The secret must have the following keys DASHBOARD_USERNAME, DASHBOARD_PASSWORD |
## and the cluster name should be the same as the {release-name}
16
-
## go to the manager.config section in the values file to see how you can add your own configuration files
16
+
## go to the manager.config.customManagerConfig section in the values file to see how you can add your own configuration files
17
17
nameOverride: ""
18
18
fullnameOverride: ""
19
19
20
20
tls:
21
-
# You either need to provide a secrete name containing specific keys as certs or enable the creation of certifications if
22
-
# your cluster supports issuing certificates.
21
+
# You either need to provide a secrete name containing specific keys as certs or enable the creation of certifications if your cluster supports cert manager.
23
22
# **REQUIRED** when you want to provide your own certificate
24
23
# The Secret name for the certs must have the following keys within it
0 commit comments