New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #21877: Hardening guide for Rudder #952
Fixes #21877: Hardening guide for Rudder #952
Conversation
447f95e
to
96c4965
Compare
PR updated with a new commit |
3 similar comments
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
PR updated with a new commit |
|
||
Now you can set your policy server with `rudder agent policy-server mypolicyserver` | ||
and the agent will only accept the connection if it matches the provided key hash. | ||
This way, once the node sends its first inventory, if it matched the node id and certificate, it will be automatically accepted. Note that this creation call also allows pre-setting node properties. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is misleading - the node is already existing within Rudder
This way, once the node sends its first inventory, if the node id and certificate match the pre-provisionned entry, the node inventory will be update.
Please note that you can also pre-defined node properties using this API, to ensure that the pre-provisionned node is already in the correct groups
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a really neat document
Some minor changes on wording are requested to make it more understandable
PR updated with a new commit |
OK, squash merging this PR |
0b9a37c
to
5b5cf89
Compare
https://issues.rudder.io/issues/21877