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

Declare resource requirements on local-env

Browse Source
This commit is contained in:
Manuel Gutierrez 2021-01-19 18:44:51 +01:00
parent 565ac7f762
commit bbfcd02b1a
No known key found for this signature in database
GPG Key ID: CEB8789DAED15AAD
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
local-environment.md
View File

@ -8,6 +8,14 @@ Here we will describe the steps unique for a deployment on a local development s
- Kubernetes cluster already deployed.
### Resource requirements
To deploy the `local-env` variant the Kubernetes cluster should have at least the following resources **available**:
- 2 CPU units
- 3 Gi of memory
- 2 Gi of storage
## Deployment
### Clone this repository.
@ -63,7 +71,7 @@ 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 and Wazuh clusters 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 its contents with different values than the base files on `wazuh/`.
By using the kustomization file on the `eks` variant we can now deploy the whole cluster with a single command: