upstream/icinga2
1
0
Fork 0
mirror of https://github.com/Icinga/icinga2.git synced 2026-05-28 04:12:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge 4015050b68 into f63bbec4ab

Browse source
This commit is contained in:
Feu Mourek 2026-05-23 16:06:08 +08:00 committed by GitHub
commit eb9db64e69
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/19-technical-concepts.md
View file

@ -578,9 +578,14 @@ This takes some minutes and requires all nodes to reconnect to each other.
There is an additional scenario: The setup on a child node does
not necessarily need a connection to the parent node.
This mode leaves the node in a semi-configured state. You need
to manually copy the master's public CA key into `/var/lib/icinga2/certs/ca.crt`
on the client before starting Icinga 2.
Running `icinga2 node setup` without using the `--parent_host` argument will leave
the node in a semi-configured state. I.e., you will need to manually copy the master's
public CA key into `/var/lib/icinga2/certs/ca.crt` on the client before starting
Icinga2. After which the TLS communication can be established.
To complete the certificate signing, the `icinga2 ca list` and `icinga2 ca sign`
commands must be used on the Icinga CA server to complete the certificate signing
process if no ticket was provided using the `--ticket` argument.
> **Note**
>