Change cluster files to make it enabled by default #13655
Merged
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.
Description
Removed cluster options:
Disabled
Key
Name
Changed default value:
nodes
is now127.0.0.1
instead ofNODE_IP
.node_name
is now the hostname instead ofnode01
(changes in core will be required as explained here).Added cluster options:
certfile
: Path to certfile (default value is/var/ossec/etc/sslmanager.cert
).keyfile
: Path to keyfile (default value is/var/ossec/etc/sslmanager.key
).keyfile_password
: Keyfile password if any (default value is '')In addition, when
127.0.0.1
is used asbind_addr
in a master node, it means that workers won't be able to connect. As a consequence, children processes creation is disabled in thewazuh-clusterd
process of the master node. Most of the tasks (Local integrity
,Local agent-groups
,Sendsync
, etc) are disabled too.Some warnings and info messages are shown in the
cluster.log
to notify all this:Coverage