This repository has been archived by the owner on Apr 18, 2023. It is now read-only.
Documentation and deployment minor tweaks #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to deploy them ! Fix Logstash LS_HEAP_SIZE VS LS_JAVA_OPTS * Set a shorter sync interval for the cluster managers * Use the Parallel pod management policy for managers since deployment order is not important * Update the mount path of the ossec.conf file
amoreauCoveo
reviewed
May 4, 2018
README.md
Outdated
| @@ -2,21 +2,23 @@ | |||
| Wazuh (3.2) cluster on top of Kubernetes (tested with 1.8.6) with a working simple ELK stack. | |||
|
|
|||
| ## Abstract | |||
| Wazuh best practices recommend to deploy multiple instances of the Wazuh manager so it can support a larger amount of events and can be fault tolerant. | |||
| Wazuh best practices recommends deploying multiple instances of the Wazuh manager so it can support a larger amount of events and can be fault tolerant. | |||
There was a problem hiding this comment.
The Wazuh best practices recommend . . .
README.md
Outdated
| @@ -77,6 +79,9 @@ Then, all the pieces should be up! | |||
| * All manager nodes of your Wazuh manager cluster should be reachable at wazuh-manager.some-domain.com:1514 | |||
| * Kibana and the Wazuh Kibana application should be available at https://wazuh.some-domain.com:443 | |||
|
|
|||
| ## Wazuh agents deployment | |||
| This repository does not show how to deploy the Wazuh agent in a Kubernetes cluster. Normally, we would use a DaemonSet to deploy the agent on each Kubernetes node. To do that, we would need a Docker image with the Wazuh agent installed on it and then we would need to mount almost every folders of the host inside that container (`/bin`, `/etc`, `/var/log`, etc.). It would be a very complicated task since you cannot simply mount the `/bin` folder of you host in the `/bin` folder of your container. Therefore, creating such Docker image an using it in a Kubernetes DaemonSet is not the ideal way to deploy a Wazuh agent. Instead, you should take a look at the [Wazuh Ansible playbooks project](https://github.com/wazuh/wazuh-ansible) or at the [Wazuh Puppet module project](https://github.com/wazuh/wazuh-puppet) to deploy your Wazuh agents. | |||
There was a problem hiding this comment.
almost every folder
... folder of your host ...
creating such Docker images and using them in . . .
There was a problem hiding this comment.
"creating such Docker images and using them in" is not the intent here. You only need one image, you don't need many. :)
amoreauCoveo
approved these changes
Jun 1, 2018
mcoulombe636
approved these changes
Jun 1, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since I created this project, some question were answered and it's time to update the code and the documentation in here.
* Update the main README, add information about Wazuh agents and how to deploy them (Fixes #3)
* Update the mount path of the ossec.conf file (see wazuh/wazuh-docker#42)
* Set a shorter sync interval for the cluster managers (see wazuh/wazuh#398 (comment))
! Fix Logstash LS_HEAP_SIZE VS LS_JAVA_OPTS (see elastic/logstash-docker#27, LS_HEAP_SIZE does not exist anymore and was replaced by LS_JAVA_OPTS)
* Use the Parallel pod management policy for managers since deployment order is not important