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

Fix local-env section

Browse Source
This commit is contained in:
Manuel Gutierrez 2021-01-28 18:42:35 +01:00
parent d2f233e6cd
commit a06614ec55
No known key found for this signature in database
GPG Key ID: CEB8789DAED15AAD
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
local-environment.md
View File

@ -71,9 +71,9 @@ The provisioner column displays `microk8s.io/hostpath`, you must edit the file `
We are using the overlay feature of kustomize two create two variants: `eks` and `local-env`, in this guide we're using `local-env`. (For a production deployment on EKS check the guide on [instructions.md](instructions.md))
It is possible to adjust resources for the cluster by editing patches on `envs/local-env/`, the number of replicas for Elasticsearch nodes and Wazuh workers are reduced on the `local-env` variant to save resources. This could be undone by removing these patches from the `kustomization.yaml` or alter its contents with different values than the base files on `wazuh/`.
It is possible to adjust resources for the cluster by editing patches on `envs/local-env/`, the number of replicas for Elasticsearch nodes and Wazuh workers are reduced on the `local-env` variant to save resources. This could be undone by removing these patches from the `kustomization.yaml` or alter the patches themselves with different values.
By using the kustomization file on the `eks` variant we can now deploy the whole cluster with a single command:
By using the kustomization file on the `local-env` variant we can now deploy the whole cluster with a single command:
```BASH
$ kubectl apply -k envs/eks/